Dell PowerVault MD3660i Series Storage Arrays Deployment Guide
Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2012 Dell Inc.
Contents Notes, Cautions, and Warnings...................................................................................................2 1 Introduction..................................................................................................................................7 System Requirements...............................................................................................................................................7 Management Station Requirements................................
Using A DHCP server........................................................................................................................................27 Using A Static IP Address................................................................................................................................27 Using A DNS Server.........................................................................................................................................28 Using A WINS Server.....................
For Windows Server 2008 GUI Version............................................................................................................42 For Windows Server 2008 Core Version...........................................................................................................42 For Linux Server...............................................................................................................................................43 Step 8: (Optional) Set Up In-Band Management..............
Introduction 1 This guide provides information about deploying Dell PowerVault MD3660i storage arrays. The deployment process includes: • Hardware installation • Modular Disk Storage Manager (MD Storage Manager) installation • Initial system configuration Other information provided include system requirements, storage array organization, and utilities. NOTE: For more information on product documentation, see support.dell.com/manuals.
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 (for example, through failure of a host server port) does not result in loss of access to data on the storage array.
Hardware Installation 2 Before using this guide, ensure that you review the instructions in the: • • • Getting Started Guide—The Getting Started Guide that shipped with the storage array, provides information to configure the initial setup of the system. Dell PowerVault MD3260/3260i/3660i/3660f/3060e Storage Arrays Administrator's Guide—The Administrator's Guide provides information about important concepts you must know before setting up your storage solution. See the Administrator's Guide at support.
Redundant And Non-Redundant Configurations Non-redundant configurations are configurations that provide only a single data path from a host to the storage array. This type of configuration is only recommended for non-critical data storage. Path failure from a failed or removed cable, a failed HBA, or a failed or removed RAID controller module results in loss of host access to storage on the storage array.
Figure 1. Four Hosts in a Dual-Controller Configuration In the following figure, up to two servers are directly attached to the RAID controller modules. 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.
Figure 2. Two Hosts Connected to Two Controllers In the following figure, up to two cluster nodes are directly attached to two RAID controller modules. Since each cluster node has redundant paths, loss of a single path still allows access to the storage array through the alternate path.
Figure 3.
Network-Attached Configurations You can also cable the host servers to the RAID controller module iSCSI ports through industry-standard 10 Gbps or 1 Gbps Ethernet switches. An iSCSI configuration that uses Ethernet switches is frequently referred to as an IP SAN. By using an IP SAN, the PowerVault MD3660i series storage array can support up to 64 hosts simultaneously. This configuration supports either single or dual path data configurations and either single or dual controller modules.
Figure 4. 64 Servers Connected to Two Controllers The following figure shows up to 64 stand-alone servers attached (using multiple sessions) to a dual RAID controller configuration through a network using a 1 Gbps to 10 Gbps aggregation scheme. The NICs on the servers are 1 Gbps NICs and the uplink ports on the 1 Gbps switches are 10 Gbps.
network allow two separate physical paths for each host, which ensures full redundancy if one of the paths fails. It is recommended you use two switches for more redundancy. However, single switch configuration is also supported. Figure 5.
Cabling PowerVault MD3060e Expansion Enclosures You can expand the capacity of your PowerVault MD3660i Series storage array by adding PowerVault MD3060e expansion enclosures. You can expand the physical disk pool to a maximum of 120 (or 180, if enabled using Premium Feature activation) physical disks using a maximum of two expansion enclosures.
15. After the PowerVault MD3060e Series expansion enclosure is configured as an expansion enclosure of the storage array, restore the data that was backed up in step 1. Expanding With New PowerVault MD3060e Expansion Enclosures Perform the following steps to attach new PowerVault MD3060e expansion enclosures to a PowerVault MD3660i Series storage array: 1. Before adding the expansion enclosure(s), ensure that the storage array software is installed and is up to date.
Installing MD Storage Manager 3 The PowerVault MD Series resource media contains software and drivers for both Linux and Microsoft Windows operating systems. The root of the media contains a readme.txt file covering changes to the software, updates, fixes, patches, and other important data applicable to both Linux and Windows operating systems. The readme.
Graphical Installation (Recommended) The MD Storage Manager configures, manages, and monitors the storage array. To install the MD storage manager: 1. Insert the PowerVault MD Series resource media. Depending on your operating system, the installer may launch automatically. If the installer does not launch automatically, navigate to the root directory of the installation media (or downloaded installer image) and run the md_launcher.exe file.
Silent Installation Silent Installation On Windows To run silent installation on a Windows system: 1. Copy the custom_silent.properties file in the /windows folder of the installation media or image to a writable location on the host server. 2. Modify the custom_silent.properties file to reflect the features, models and installation options to be used. Then, save the file. 3. After the custom_silent.
Post Installation Tasks 4 Before using the storage array for the first time, complete a number of initial configuration tasks in the order shown. These tasks are performed using the MD Storage Manager. NOTE: If Dynamic Host Configuration Protocol (DHCP) is not used, initial configuration using the management station must be performed on the same physical subnet as the storage array.
iSCSI Configuration Worksheet The IPv4 Settings — Worksheet and IPv6 Settings — Worksheet helps you plan your configuration. Recording host server and storage array IP addresses at a single location enables you to configure your setup faster and more efficiently. Guidelines For Configuring Your Network For iSCSI provides general network setup guidelines for both Windows and Linux environments. It is recommended that you review these guidelines before completing the worksheet.
Storage Array Configuration Before a host iSCSI initiator and an iSCSI-based storage array can communicate, they must be configured with information such as which IP addresses and authentication method to use. Since iSCSI initiators establish connections with an already configured storage array, the first task is to configure your storage arrays to make them available for iSCSI initiators. This utility requires network access to the management ports of the storage arrays you wish to configure.
• For redundancy in a dual controller (duplex) configuration, ensure each host network interface is configured to connect to both storage array controllers. • For optimal load balancing, ensure each host network interface that is used for iSCSI traffic is configured to connect to each storage array controller. • It is recommended that each host network interface only establishes one iSCSI session per storage array controller.
Guidelines For Configuring Your Network For iSCSI 5 This section provides general guidelines for setting up your network environment and IP addresses for use with the iSCSI ports on your host server and storage array. Your specific network environment may require different or additional steps than shown here, so make sure you consult with your system administrator before performing this setup.
3. Restart network services using the following command: /etc/init.d/network restart Using A DNS Server If you are using static IP addressing: 1. In the Control Panel, select Network connections or Network and Sharing Center and then click Manage network connections. 2. Right-click the network connection you want to configure and select Properties. 3.
NETWORKING=yes HOSTNAME=mymachine.mycompany.com 2. Edit the configuration file for the connection you want to configure, either /etc/sysconfig/network-scripts/ifcfg-ethX (for Red Hat Enterprise Linux) or /etc/sysconfig/network/ifcfg-eth-id-XX:XX:XX:XX:XX (for SUSE Enterprise Linux). BOOTPROTO=dhcpm Also, verify that an IP address and netmask are not defined. 3. Restart network services using the following command: /etc/init.
Uninstalling MD Storage Manager 6 Uninstalling MD Storage Manager From Windows Uninstall MD Storage Manager From Microsoft Windows Operating Systems Other Than Microsoft Windows Server 2008 Use the Change/Remove Program feature to uninstall the Modular Disk Storage Manager from Microsoft Windows operating systems other than Microsoft Windows Server 2008. To uninstall the Modular Disk Storage Manager from Microsoft Windows Server 2008: 1. Double-click Add or Remove Programs from the Control Panel. 2.
Uninstalling MD Storage Manager From Linux By default, PowerVault MD Storage Manager is installed in the /opt/dell/mdstoragemanager directory. If another directory was used during installation, navigate to that directory before beginning the uninstallation procedure. 1. From the installation directory, open the Uninstall Dell MD Storage Software directory. 2. Run the file Uninstall Dell MD Storage Software.exe. 3. From the Uninstall window, click Next, and follow the instructions on the screen.
Appendix — Manual Configuration Of iSCSI 7 The following sections contain step-by-step instructions for configuring iSCSI on your storage array. However, before beginning, it is important to understand where each of these steps occur in relation to your host server or storage array environment. The table below shows each iSCSI configuration step and where it occurs.
You can discover the storage array either automatically or manually. Automatic Storage Array Discovery 1. Launch MD Storage Manager. If this is the first storage array to be set up, the Add New Storage Array window is displayed. 2. Select Automatic and click OK. After discovery is complete, a confirmation screen is displayed. It may take several minutes for the discovery process to complete. Closing the discovery status window before the discovery process completes cancels the discovery process. 3.
Task Purpose degrades or fails, or an adverse environmental condition occurs. Configure a storage array To create virtual disks and map them to hosts. Step 2: Configure The iSCSI Ports On The Storage Array By default, the iSCSI ports on the storage array are set to the following IPv4 settings: Controller 0, Port 0: IP: 192.168.130.101 Subnet Mask: 255.255.255.0 Controller 0, Port 1: IP: 192.168.131.101 Subnet Mask: 255.255.255.0 Controller 1, Port 0: IP: 192.168.130.102 Subnet Mask: 255.255.255.
3. Under Target Portals, click Add 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.
d) Save and close the /etc/iscsi/iscsid.conf file. 5. From the console, restart the iSCSI service with the following command: service iscsi start 6. Verify that the iSCSI service is running during boot using the following command from the console: chkconfig iscsi on 7. To display the available iSCSI targets at the specified IP address, use the following command: iscsiadm –m discovery –t st -p 8.
Mutual CHAP In addition to setting up target CHAP, you can set up mutual CHAP in which both the storage array and the iSCSI initiator authenticate each other. To set up mutual CHAP, configure the iSCSI initiator with a CHAP secret that the storage array must send to the host sever in order to establish a connection. In this two-way authentication process, both the host server and the storage array send information that the other must validate before a connection is allowed.
CHAP Setting Description CHAP If CHAP is selected and None is deselected, the storage array requires CHAP authentication before allowing access. 2. To configure a CHAP secret, select CHAP and select CHAP Secret. 3. Enter the Target CHAP Secret (or Generate Random Secret). Confirm it in Confirm Target CHAP Secret and click OK. Although the storage array allows sizes from 12 to 57 characters, many initiators only support CHAP secret sizes up to 16 characters (128-bit).
The iSCSI port you configured on the storage array during target discovery disappears. 6. Under Target Portals, click Add 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: – Local Adapter — Should always be set to Microsoft iSCSI Initiator. – Source IP — The source IP address of the host you want to connect with.
3. If you are using Mutual CHAP authentication, you can set the user name and password for CHAP authentication of the target(s) by the initiator by editing the following lines: node.session.auth.username_in= node.session.auth.password_in = 4. To set up discovery session CHAP authentication, first uncomment the following line: discovery.sendtargets.auth.authmethod = CHAP 5.
Step 7: Connect To The Target Storage Array From The Host Server For Windows Server 2008 GUI Version 1. Click Start → Program → 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 Log On. 4. Select Automatically restore this connection when the system boots. 5. Select Enable multi-path. 6.
TCP_Port_Number_Of_Target_Portal * * * Login_Flags * * * * * Username Password Authtype * Mapping_Count where – is the target name as displayed in the target list. Use the iscsicli ListTargets command to display the target list. – is T, which exposes the LUN to the operating system as a storage device. – is the IP address of the iSCSI port on the controller being logged in to. – is 3260.
Step 8: (Optional) Set Up In-Band Management Out-of-band management (see Step 1: Discover the Storage Array (Out-of-band Management Only) ) is the recommended method for managing the storage array. However, to optionally set up in-band management, use the steps shown below. The default iSCSI host port IPv4 addresses are displayed below for reference: Controller 0, Port 0: IP: 192.168.130.101 Controller 192.168.131.101 Controller 0, Port 0: IP: 192.168.132.101 Controller 192.168.133.
Appendix — Using Internet Storage Naming Service 8 Internet Storage Naming Service (iSNS) server, supported only on Microsoft Windows iSCSI environments, eliminates the need to manually configure each individual storage array with a specific list of initiators and target IP addresses. Instead, iSNS automatically discovers, manages, and configures all iSCSI devices in your environment. For more information on iSNS, including installation and configuration, see microsoft.com.
Appendix — Load Balancing 9 Windows Load Balance Policy Multi-path drivers select the I/O path to a virtual disk through a specific RAID controller module. When the multi-path driver receives a new I/O, the driver tries to find a path to the current RAID controller module that owns the virtual disk. If that path cannot be found, the multi-path driver migrates the virtual disk ownership to the secondary RAID controller module.
The Computer Management window is displayed. 2. Click Device Manager to show the list of devices attached to the host. 3. Right-click the multi-path disk device for which you want to set load balance policies, then select Properties. 4. From the MPIO tab, select the load balance policy you want to set for this disk device. Changing The Load Balance Policy Using The Windows Server 2008 Disk Management Options 1. From the host desktop, right-click My Computer and select Manage.
Figure 6. Initiator Configuration Two sessions with one TCP connection are configured from the host to each controller (one session per port), for a total of four sessions. The multi-path failover driver balances I/O access across the sessions to the ports on the same controller. In a duplex configuration, with virtual disks on each controller, creating sessions using each of the iSCSI data ports of both controllers increases bandwidth and provides load balancing.
Appendix — Stopping And Starting iSCSI Services In Linux 10 To manually stop the iSCSI services in Linux, certain steps must be followed to maintain parallel processing between the storage array and the host server. 1. Stop all I/O. 2. Unmount all correlated file systems. 3. Stop iSCSI service by running the following command: /etc/init.
11 IPv4 Settings — Worksheet NOTE: If you need additional space for more than one host server, use an additional sheet. Static IP address (host server) Subnet (should be different for each NIC) Default gateway iSCSI port 1 ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ iSCSI port 2 ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ Management port ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ Management port ___ . ___ . ___ . ___ ___ .
Static IP address (host server) Subnet Default gateway iSCSI port 1, In 0 ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ iSCSI port 1, In 1 ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ Management port cntrl 1 ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ .
12 IPv6 Settings — Worksheet NOTE: If you need additional space for more than one host server, use an additional sheet. Host iSCSI port 1 Host iSCSI port 2 Link local IP address ___ . ___ . ___ . ___ Link local IP address ___ . ___ . ___ . ___ Routable IP address ___ . ___ . ___ . ___ Routable IP address ___ . ___ . ___ . ___ Subnet prefix ___ . ___ . ___ . ___ Subnet prefix ___ . ___ . ___ . ___ Gateway ___ . ___ . ___ . ___ Gateway ___ . ___ . ___ .
Router IP address ____ : ____ : ____ : ____ : ____ : ____ : ____ : ____ iSCSI controller 0, In 1 IP address FE80 : 0000 : 0000 : 0000 : ____ : ____ : ____ : ____ Routable IP address 1 ____ : ____ : ____ : ____ : ____ : ____ : ____ : ____ Routable IP address 2 ____ : ____ : ____ : ____ : ____ : ____ : ____ : ____ Router IP address ____ : ____ : ____ : ____ : ____ : ____ : ____ : ____ iSCSI controller 1, In 0 IP address FE80 : 0000 : 0000 : 0000 : ____ : ____ : ____ : ____ Routable IP address 1 _
