Dell PowerVault MD3860i 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. Copyright © 2016 Dell Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents 1 Introduction........................................................................................................... 6 System Requirements............................................................................................................................6 Management Station Requirements............................................................................................... 6 Introduction To Storage Arrays...........................................................................
Microsoft Windows Host Setup..........................................................................................................28 Using A DHCP server.....................................................................................................................28 Using A Static IP Address.............................................................................................................. 28 Using A DNS Server...............................................................................
Connect To The Target Storage Array From the Host Server Using Windows Server GUI........42 Connect To The Target Storage Array From the Host Server Using Windows Server Core Version........................................................................................................................................... 43 For Linux Server.............................................................................................................................
Introduction 1 This guide provides information about deploying Dell PowerVault MD3860i 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 Related Documentation.
• Host server — On a host server system, MD Storage Manager and the storage array communicate management requests and event information using in-band or out-of-band connections. • Management station — On a management station, MD Storage Manager communicates with the storage array either through an Ethernet connection to the storage array management port or through an Ethernet connection to a host server.
Hardware Installation 2 Before using this guide, ensure that you review the instructions in the: • Dell PowerVault MD3460/MD3860i/MD3860f Storage Arrays Getting Started Guide — The Getting Started Guide that is shipped with the storage array provides information to configure the initial setup of the system. • Dell PowerVault MD Series Storage Arrays Administrator's Guide — The Administrator's Guide provides information about important concepts you must know before setting up your storage solution.
Each PowerVault MD3860i series storage array can be expanded to a maximum of 120 (or 180, if enabled using Premium Feature activation) physical slots through a maximum of two PowerVault MD3060e series expansion enclosures. Cabling The Storage Array The iSCSI interface enables different host-to-controller configurations.
Figure 1. Four Hosts in a Dual-RAID 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 RAID 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 RAID Controllers In the following figure, up to two cluster nodes are directly attached to two RAID controller modules. Each cluster node has redundant paths, loss of a single path still allows access to the storage array through the alternate path.
Figure 3. Two Cluster Nodes Connected to Two RAID Controllers Network-Attached Configurations You can also cable the host servers to the RAID controller module iSCSI ports through industry-standard 10 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 MD3860i series storage array can support up to 64 hosts simultaneously.
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 4. 64 Servers Connected to Two RAID Controllers Remote Replication Remote Replication is a storage array premium feature that provides online, real-time replication of data between storage arrays. The following figure shows an example of how to setup a Remote Replication environment.
Figure 5. Remote Replication Environment Mixed Environment The following figure shows mixed configuration, that is direct attachment via SAS to one host connectivity to another host via direct attached iSCSI or the IP SAN. Figure 6.
Cabling PowerVault MD3060e Expansion Enclosures You can expand the capacity of your PowerVault MD3860i Series storage array by adding PowerVault MD3060e expansion enclosures. You can expand the physical disk drive pool to a maximum of 120 (or 180, if enabled using Premium Feature activation) physical disk drives using a maximum of two expansion enclosures. To connect the MD3060e expansion enclosure to your MD Series Dense RAID storage array, refer to the diagrams given here.
MD3060e Expansion cabling diagrams Figure 7.
Figure 8. Dual Expansion Cabling Diagram Expanding With New PowerVault MD3060e Expansion Enclosures NOTE: Hot plug of MD3060e expansion enclosure is not recommended. Power on all MD3060e expansion enclosures before you power on the array enclosure. For helpful videos and other resources on PowerVault MD series, see dell.com/PVresources. Perform the following steps to attach new PowerVault MD3060e expansion enclosures to a PowerVault MD3860i Series storage array: 1.
For information about installing the software, see Installing MD Storage Manager. 3. Using MD Storage Manager, update the RAID controller module firmware and NVSRAM to the latest versions available on dell.com/support. 4. Click Tools → Upgrade RAID Controller Module Firmware from the Enterprise Management Window (EMW) by selecting the array enclosure that you want to update. 5. Stop all I/O to the storage array and turn off affected host systems attached to the storage array. 6.
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 describing changes to the software, updates, fixes, patches, and other important data applicable to both Linux and Windows operating systems. The readme.
The PowerVault MD Series resource media offers the following installation methods: • Graphical Installation (Recommended) — This is the recommended installation procedure. The installer presents a graphical wizard-driven interface that allows customization of components installed. • Console Installation — This installation procedure is useful for Linux users who do not desire to install an X-Window environment on their supported Linux platform.
8. When reboot is complete, if the MDCU does not launch automatically, launch it manually. a. In a Windows-based operating system, click Start → Dell → Modular Disk Configuration Utility. b. In a Linux-based operating system, double-click the Modular Disk Configuration Utility icon on the desktop. 9. Establish the iSCSI initiator. 10. Start MD Storage Manager and discover the array(s).
NOTE: On Red Hat Enterprise Linux 6 operating systems, run the following script from the root directory to install prerequisite packages: # md_prereq_install.sh 1. Copy the custom_silent.properties file in the /linux directory 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.
Term Definition iSNS (Microsoft Internet Storage Naming Service) An automated discovery, management and configuration Storage Naming Service tool used by some iSCSI devices. Management station The system from which you manage your host server/storage array configuration. Storage array The enclosure containing the storage data accessed by the host server. Target An iSCSI port on the storage array that accepts and responds to requests from the iSCSI initiator installed on the host server.
This Step is Performed on the Host Server Using the Microsoft or Linux iSCSI Initiator This Step is Performed on the Storage Array Using PowerVault MD Storage Manager 8. (Optional) Set up in-band management NOTE: It is recommended that you use the PowerVault Modular Disk Configuration Utility (MDCU) for iSCSI configuration. The PowerVault MDCU wizards guides you through the configuration steps described above. If you want to perform a manual configuration, see Appendix — Manual Configuration of iSCSI.
The option to configure a host is disabled if the machine the utility is running on does not have an iSCSI initiator or the required driver components installed. When the option is disabled, the utility also displays an informational message. If you are running the utility on a host which is not connected to the iSCSI based storage array (or which you do not wish to connect to the array), the informational message can be ignored. The task involves the following steps: 1.
5. Complete the steps in Config Wizard to configure your iSCSI storage array. 6. In the Array Configuration Summary window, review and apply your configuration settings. 7. Click Create iSCSI Sessions, to create host-to-storage array communication. Repeat for all host-to-array mappings you want to implement. 8. Verify that communication is established between the storage array and host server. NOTE: For more information on MDCU, see the MDCU online Help.
5 Guidelines For Configuring Your Network For iSCSI 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. NOTE: Ensure all your network components have flow control enabled.
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. On the General tab (for a local area connection) or the Networking tab (for all other connections), select Internet Protocol (TCP/IP), and then click Properties. 4.
Also, verify that an IP address and netmask are not defined. 3. Restart network services using the following command: /etc/init.d/network restart Using A Static IP Address If you are using a static IP address (root users only): 1. Edit the /etc/sysconfig/network file as follows: NETWORKING=yes HOSTNAME=mymachine.mycompany.com GATEWAY=255.255.255.0Ž 2.
Uninstalling MD Storage Manager 6 Uninstalling MD Storage Manager From Windows To uninstall the Modular Disk Storage Manager from Microsoft Windows Server: 1. Double-click Add or Remove Programs from the Control Panel. 2. Select Dell MD Storage Software from the list of programs. 3. Click Change/Remove. The Uninstall Complete window is displayed. 4. Follow the instructions on screen. 5. Select Yes to restart the system, and then click Done.
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.
NOTE: If DHCP is not used, initial configuration using the management station must be performed on the same physical subnet as the storage array. Additionally, during initial configuration, at least one network adapter must be configured on the same IP subnet as the storage array’s default management ports (RAID Controller 0 MGMT (port 0): 192.168.128.101 or RAID Controller 1 MGMT (port 0): 192.168.128.102).
3. Click the Initial Setup Tasks option to see links to the remaining post-installation tasks. For more information about each task, see the Administrator's Guide at dell.com/powervaultmanuals. Perform these tasks in the order shown in the following table. Task Purpose Rename the storage array To provide a more meaningful name than the software-assigned label, Unnamed. Set a storage array password To restrict unauthorized access.
• 3. Jumbo frames — Jumbo Ethernet frames are created when the maximum transmission units (MTUs) are larger than 1500 bytes per frame. This setting is adjustable port-by-port. To enable ICMP PING responses for all ports, select Enable ICMP PING responses. 4. Click OK when all iSCSI storage array port configurations are complete. 5. Test the connection for each iSCSI storage array port.
To use the sample file included on the resource media: 1. Save the default /etc/iscsi/iscsid.conf file by naming it to another name of your choice. 2. Copy the appropriate sample file from /linux/etc on the media to /etc/iscsi/iscsid.conf. 3. Rename the sample file to iscsid.conf. 4. Edit the following entries in the /etc/iscsi/iscsid.conf file: a. Edit or verify that the node.startup = manual line is disabled. b. Edit or verify that the node.startup = automatic line is enabled.
Understanding CHAP Authentication What Is CHAP Challenge Handshake Authentication Protocol (CHAP) is an optional iSCSI authentication method where the storage array (target) authenticates iSCSI initiators on the host server. Two types of CHAP are supported: • Target CHAP • Mutual CHAP Target CHAP In target CHAP, the storage array authenticates all requests for access issued by the iSCSI initiator(s) on the host server using a CHAP secret.
Step 5: Configure CHAP Authentication On The Storage Array (Optional) If you are not configuring any type of CHAP, skip these steps and go to Step 7: Connect To The Target Storage Array From The Host Server. NOTE: If you choose to configure mutual CHAP authentication, you must first configure target CHAP. In terms of iSCSI configuration, the term Target always refers to the storage array. Configuring Target CHAP Authentication On The Storage Array 1.
• CHAP — Select CHAP if you want to enable an initiator that tries to access the target to authenticate using CHAP. Define the CHAP secret only if you want to use mutual CHAP authentication. If you select CHAP, and if no CHAP target secret is defined, an error message is displayed. Click CHAP Secret to view the Enter CHAP Secret windows. Use this window to define the CHAP secrets. NOTE: To remove a CHAP secret, you must delete the host initiator and add it again.
Configure CHAP Authentication On The Host Server Using Windows Server Core Version 1. Set the iSCSI initiator services to start automatically (if not already set): sc \\ config msiscsi start=auto. 2. Start the iSCSI service (if necessary): sc start msiscsi. 3. If you are not using mutual CHAP authentication, go to step 5. 4. Enter the mutual CHAP secret you entered for the storage array: iscsicli CHAPSecret . 5.
03.com.redhat01.78b1b8cad821 discovery.sendtargets.auth.password = password_1 discovery.sendtargets.auth.username = iqn.1984- 05.com.dell:powervault. 123456discovery.sendtargets.auth.password_in = test1234567890 Configure CHAP Authentication On The Host Server Using SUSE Linux Enterprise Server GUI 1. Click Desktop→ YaST→ iSCSI Initiator. 2. Click Service Start, then select When Booting. 3. Select Discovered Targets, then select Discovery. 4. Enter the IP address of the port. 5. Click Next. 6.
NOTE: IPSec is not supported. 7. Click OK. To support storage array controller failover, the host server must be connected to at least one iSCSI port on each RAID controller. Repeat step 3 through step 8 for each iSCSI port on the storage array that you want to establish as failover targets. The Target Portal address is different for each port you connected to.
establish as a failover target. The Target_ Portal_Address is different for each port you connect to. PersistentLoginTarget does not initiate a login to the target until after the system is rebooted. To establish immediate login to the target, substitute LoginTarget for PersistentLoginTarget. NOTE: See the Microsoft iSCSI Software Initiator 2.x User’s Guide for more information about the commands used in the previous steps.
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.
Load Balancing 9 Load Balance Policy Multi-path drivers select the I/O path to a virtual disk through a specific RAID controller module. When the multi-path driver receives a new I/O to process, the driver tries to find a path to the current RAID controller module that owns the virtual disk. If the path to the current RAID controller module that owns the virtual disk cannot be found, the multi-path driver migrates the virtual disk ownership to the secondary RAID controller module.
If more than one data path to the virtual disk has the same weight value, the round robin with subset path selection policy is used to route I/O requests between the paths with the same weight value. The least path weight load balance policy is not supported on Linux operating systems. Increasing Bandwidth With Multiple iSCSI Sessions The PowerVault MD3860i series storage array in a duplex configuration supports two active/active asymmetric redundant RAID controllers.
10 Appendix — Stopping And Starting iSCSI Services In Linux 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 0, In 0 ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ iSCSI port 0, In 1 ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ Management port cntrl 0 ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ iSCSI port 1, In 0 ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ ___ . ___ . ___ . ___ iSCSI port 1, In 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 ___ . ___ . ___ .
iSCSI RAID controller 0, In 0 IP address FE80 : 0000 : 0000 : 0000 : ____ : ____ : ____ : ____ Routable IP address 1 ____ : ____ : ____ : ____ : ____ : ____ : ____ : ____ Routable IP address 2 ____ : ____ : ____ : ____ : ____ : ____ : ____ : ____ Router IP address ____ : ____ : ____ : ____ : ____ : ____ : ____ : ____ iSCSI RAID controller 0, In 1 IP address FE80 : 0000 : 0000 : 0000 : ____ : ____ : ____ : ____ Routable IP address 1 ____ : ____ : ____ : ____ : ____ : ____ : ____ : ____ Routable I
Getting help 13 Contacting Dell Dell provides several online and telephone-based support and service options. If you do not have an active internet connection, you can find contact information on your purchase invoice, packing slip, bill, or Dell product catalog. Availability varies by country and product, and some services may not be available in your area. To contact Dell for sales, technical assistance, or customer-service issues: 1. Go to Dell.com/support. 2.
