MDSM enables an administrator to configure and monitor storage arrays for optimum usability. The version of MDSM included on the PowerVault MD series resource media can be used to manage both the PowerVault MD3200 series and the earlier PowerVault MD series storage arrays. MDSM is compatible with both Microsoft Windows and Linux operating systems.
NOTE: Supported hypervisors include Microsoft Hyper-V, Citrix XenServer, and VMware ESX and ESXi. For information about the supported versions, see Support Matrix at dell.com/support/manuals. • Administrator or equivalent permissions. Introduction to Storage Arrays An enclosure containing physical disks accessed through RAID controller modules is called a storage array.
Page 9
You can set a specified RAID level for each disk group and virtual disk on your storage array. For more information about using RAID and managing data in your storage solution, see the Owner’s Manual at dell.com/support/manuals. Introduction...
Planning section of the Owner’s Manual—The planning section provides information about important concepts you must know before setting up your storage solution. See the Owner’s Manual at dell.com/support/manuals. Planning the Storage Configuration Consider the following before installing your storage array: •...
For more information, see the Getting Started Guide. Each Dell PowerVault MD3200 series storage array can be expanded to a maximum of 120 (or 192, if enabled through the Premium Feature activation) physical disks through a maximum of seven PowerVault MD1200 series expansion enclosures.
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.
Page 14
Figure 2-2. Two Hosts Connected to a Single Controller Server 1 Server 2 Storage array Corporate, public, or private network Hardware Installation...
Page 15
Figure 2-3. Four Hosts Connected to a Single Controller Server 1 Server 2 Server 3 Server 4 Storage array Corporate, public, or private network Hardware Installation...
Dual Controller Configurations Figure 2-4 through Figure 2-6 show two and four hosts, each connected to two RAID controller modules. Since each host has redundant paths, loss of a single path would still allow access to the storage array through the alternate path. Figure 2-4.
Page 17
Figure 2-5. Four Hosts Connected to Two Controllers Server 3 Server 4 Server 1 Server 2 Storage array Corporate, public, or private network Hardware Installation...
Page 18
Figure 2-6. Four Hosts Connected to Two Controllers Server 1 Server 2 Server 3 Server 4 Storage array Corporate, public, or private network Hardware Installation...
Page 19
Figure 2-7 shows eight hosts, each connected to only one RAID controller module. This configuration allows the maximum number of hosts that may be connected, but provides no redundancy. Figure 2-7. Eight Hosts Connected to Two Controllers Up to 8 hosts Server 3 Server 4 Server 1...
Page 20
Figure 2-8 and Figure 2-9 show up to four cluster nodes connected to two RAID controller modules. Since each cluster node has redundant paths, loss of a single path would still allow access to the storage array through the alternate path. Figure 2-8.
Page 21
Figure 2-9. Four Cluster Nodes Connected to Two Controllers Four cluster nodes Storage array Corporate, public, or private network Hardware Installation...
CAUTION: If a PowerVault MD1200 series enclosure that was previously attached to PERC H800 adapter is used as an expansion enclosure to a PowerVault MD3200 series storage array, the physical disks of the expansion enclosure are reinitialized and data is lost. You must backup all data on the expansion enclosure before attempting the expansion.
Page 23
For information about installing the software, see "Installing PowerVault MD Storage Software" on page 27. Update the storage array RAID controller module firmware and NVSRAM to the latest versions available at dell.com/support, using PowerVault MDSM. Click Tools Upgrade RAID Controller Module Firmware in the Enterprise Management Window (EMW).
Expanding With New PowerVault MD1200 Series Expansion Enclosures Perform the following steps to attach new PowerVault MD1200 series expansion enclosures to a PowerVault MD3200 series storage array: 1 Before adding the expansion enclosure(s), ensure that the storage array software is installed and is up to date. For more information, see the Support Matrix at dell.com/support/manuals.
Page 25
• If the status LEDs are blinking amber, there is an error that can be viewed using PowerVault MDSM. • If the status LEDs are solid blue, the storage array is ready. After the storage array is online and ready, turn on any attached host systems.
Installing PowerVault MD Storage Software The Dell PowerVault MD series resource media contains software and drivers for both Linux and Microsoft Windows operating systems. The root of the media contains a readme.txt file covering changes to the software, updates, fixes, patches, and other important data applicable to both the Linux and Windows operating systems.
• Console Installation—This installation procedure is useful for Linux users who do not want to install an X-Window environment on their supported Linux platform. • Silent Installation—This installation procedure is useful for users who want to create scripted installations. Graphical Installation (Recommended) The PowerVault MD Storage Manager application configures, manages, and monitors the storage array.
The MD Storage Manager installer automatically installs the required drivers, firmware, and operating system patches/hotfixes to operate your storage array. These drivers and firmware are also available at dell.com/support. See the Support Matrix at dell.com/support/manuals for any additional settings and/or software required for your specific storage array.
# md_prereq_install.sh 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. 3 Save the file.
Post Installation Tasks Before using the storage array for the first time, complete the 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.
Table 4-1. Standard Terminology Used in iSCSI Configuration Term Definition iSCSI initiator The iSCSI-specific software installed on the host server that controls communications between the host server and the storage array. iSCSI host port The iSCSI port (two per controller) on the storage array.
IPv4 Settings—Worksheet host server Mutual CHAP Secret 192.168.128.101 (management network port) 192.168.131.101 (In 1 default) Target CHAP 192.168.130.101 (In 0 default) PowerVault Secret MD36 192.168.130.102 (In 0 default) 192.168.128.102 (management network port) 192.168.131.102 (In 1 default) If you need additional space for more than one host server, use an additional sheet. Subnet Static IP address (host server) Default gateway...
IPv6 Settings—Worksheet Host server Mutual CHAP Target CHAP PowerVault MD36 If you need additional space for more than one host server, use an additional sheet. Host iSCSI port 1 Host iSCSI port 2 ___ . ___ . ___ . ___ ___ .
Table 4-2. Host Server Vs. Storage Array This Step is Performed on the Host Server This Step is Performed on the Storage Using the Microsoft or Linux iSCSI Initiator Array Using PowerVault MD Storage Manager Discover the storage array Configure the iSCSI ports on the storage array Perform target discovery from the iSCSI initiator...
Page 37
The MDCU performs: • Storage array configuration • Host configuration 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.
Page 38
Keep the following guidelines in mind for the storage array and host configuration: • For optimal performance, ensure your network configuration.See the storage array's Support Matrix at dell.com/support/manuals. • If your host has multiple network interfaces, it is recommended that each network interface uses a separate subnet.
MD Storage Manager and these virtual disks can be utilized by the host server(s). For more information about storage planning and using MD Storage Manager, see the Administrator's Guide at dell.com/support/manuals. Post Installation Tasks...
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. In order for hosts to communicate with management and/or iSCSI ports of storage arrays, local NICs must be configured with IP addresses capable of communication with the addresses listed in the IPv4/IPv6 worksheet.
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 Select Use the following IP address and enter the IP address, subnet mask, and default gateway addresses.
7 To specify the location of the file that you want to import into the Lmhosts file, select Import LMHOSTS and then select the file in the Open dialog box. 8 Enable or disable NetBIOS over TCP/IP. If using Microsoft Windows Server 2008 Core Version, use the netsh interface command to configure the iSCSI ports on the host server.
Page 43
NETWORKING=yes HOSTNAME=mymachine.mycompany.com GATEWAY=255.255.255.0 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=static BROADCAST=192.168.1.255 IPADDR= 192.168.1.100 NETMASK=255.255.255.0 NETWORK= 192.168.1.0 ONBOOT=yes TYPE=Ethernet HWADDR=XX:XX:XX:XX:XX:XX GATEWAY=192.168.1.1 3 Restart network services using the following command: /etc/init.d/network restart Post Installation Tasks...
Storage Software (MDSM) from Microsoft Windows operating systems other than Microsoft Windows Server 2008: 1 Double-click Add or Remove Programs from the Control Panel. 2 Select Dell MD32xxi storage software from the list of programs. 3 Click Change/Remove. The Uninstall Complete window is displayed.
/opt/dell/mdstoragemanager directory. If another directory was used during installation, navigate to that directory before beginning the uninstallation procedure. 2 From the installation directory, open the Uninstall Dell MD Storage Software directory. 3 Run the file Uninstall Dell MD Storage Software.exe.
4 Select your business segment. The main support page for the selected business segment is displayed. 5 Select the appropriate option depending on your requirement. NOTE: If you have purchased a Dell system, you may be asked for the Service Tag. Getting Help...
Documentation Feedback If you have feedback for this document, write to documentation_feedback@dell.com. Alternatively, you can click on the Feedback link in any of the Dell documentation pages, fill up the form, and click Submit to send your feedback. Getting Help...
Appendix—Load Balancing 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.
RAID controller module that owns the virtual disk. Changing Load Balance Policies in Windows Sever 2008 Load balancing with the PowerVault MD3200 series is only available for Windows Server 2008 and later versions of the operating system. You can change the load balance policies from the default round robin with subset by using one of the following: •...
Changing the Load Balance Policy Using the Windows Server 2008 Disk Management Options 1 Right-click My Computer from the host desktop and select Manage to open the Computer Management window. 2 Click Disk Management to show the list of virtual disks attached to the host.
Appendix—Manual Configuration of iSCSI 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 the storage array environment. Table B-1 shows each iSCSI configuration step and where it occurs.
Step 1: Discover the Storage Array (Out-of-band Management Only) Default Management IPv4 Port Settings By default, the storage array management ports are set to Dynamic Host Configuration Protocol (DHCP). If the controller(s) on your storage array is unable to get IP configuration from a DHCP server, it times out after approximately three minutes and falls back to a default static IP address.
4 Finally, add the last three bytes of the MAC address FE80::0200:08FF:FEAA:BBCC. NOTE: This procedure applies to out-of-band management only. If you choose to set up in-band management, you must complete this step and then proceed to "Step 8: (Optional) Set Up In-Band Management" on page 72. You can discover the storage array either automatically or manually.
Before configuring the storage array, check the status icons on the Summary tab to ensure that the enclosures in the storage array are in an Optimal Owner’s Manual status. For more information on the status icons, see the dell.com/support/manuals. Appendix—Manual Configuration of iSCSI...
Set up alert notifications To notify individuals (by e-mail) and/or storage enterprise management consoles, such as Dell Set up e-mail alerts Management Console, (by SNMP) when a Set up SNMP alerts storage array component degrades or fails, or an adverse environmental condition occurs.
Page 58
Controller 1, Port 2: IP: 192.168.132.102 Subnet Mask: 255.255.255.0 Port: 3260 Controller 1, Port 3: IP: 192.168.133.102 Subnet Mask: 255.255.255.0 Port: 3260 NOTE: No default gateway is set. To configure the iSCSI ports on the storage array: 1 From MDSM, navigate to the Setup tab on the AMW. 2 Click configure Ethernet management ports and then select Configure iSCSI Host Ports.
Step 3: Perform Target Discovery From the iSCSI Initiator This step identifies the iSCSI ports on the storage array to the host server. Select the set of steps in one of the following sections (Microsoft Windows or Linux) that corresponds to your operating system. If you are using Microsoft Windows Server 2003 or Windows Server 2008 GUI version: 1 Click StartProgramsMicrosoft iSCSI Initiator or click StartAll...
Page 60
• If you do not plan to configure CHAP authentication, repeat step 1 thorough step 6 for all iSCSI ports on the storage array. If you are using Windows Server 2008 Core Version: 1 Set the iSCSI initiator service to start automatically: sc \\<server_name>...
5 To display the available iSCSI targets at the specified IP address, use the following command: iscsiadm –m discovery –t st -p <IP_address_of_iSCSI_port> 6 After target discovery, use the following command to manually log in: iscsiadm -m node –l This login is performed automatically at startup if automatic startup 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.
CHAP Definitions To summarize the differences between target CHAP and mutual CHAP authentication, see Table B-3. Table B-3. CHAP Types Defined CHAP Type Description Target CHAP Sets up accounts that iSCSI initiators use to connect to the target storage array. The target storage array then authenticates the iSCSI initiator.
Although the storage array allows sizes from 12 to 57 characters, many initiators only support CHAP secret sizes up to 16 characters (128-bit). NOTE: A CHAP secret is not retrievable after it is entered. Ensure that you record the secret in an accessible place. If Generate Random Secret is used, copy and paste the secret into a text file for future reference since the same CHAP secret is used to authenticate any new host servers you may add to the storage array.
Step 6: Configure CHAP Authentication on the Host Server (Optional) If you configured CHAP authentication in "Step 5: Configure CHAP Authentication on the Storage Array (Optional)" on page 63, complete the following steps. If not, skip to "Step 7: Connect to the Target Storage Array From the Host Server"...
Page 66
• Perform mutual authentication—If mutual CHAP authentication is configured, select this option. NOTE: IPSec is not supported. 8 Click OK. If you require a discovery session failover, repeat step 5 and step 6 (in this procedure) for all iSCSI ports on the storage array. Otherwise, single-host port configuration is sufficient.
Page 67
1 To enable CHAP (optional), the following line needs to be enabled in your /etc/iscsi/iscsid.conf file: node.session.auth.authmethod = CHAP 2 To set a user name and password for CHAP authentication of the initiator by the target(s), edit the following lines: node.session.auth.username = <iscsi_initiator_username>...
Page 68
7 The final configuration contained in the /etc/iscsi/iscsid.conf file might look like this: node.session.auth.authmethod = CHAP node.session.auth.username = iqn.2005- 03.com.redhat01.78b1b8cad821 node.session.auth.password password_1 node.session.auth.username_in= iqn.1984- 05.com.dell:powervault.123456 node.session.auth.password_in test1234567890 discovery.sendtargets.auth.authmethod CHAP discovery.sendtargets.auth.username = iqn.2005- 03.com.redhat01.78b1b8cad821 discovery.sendtargets.auth.password password_1 discovery.sendtargets.auth.username = iqn.1984- 05.com.dell:powervault.123456 discovery.sendtargets.auth.password_in =...
7 Select one: • If you are not using CHAP authentication, select No Authentication. Go to step 8. • If you are using CHAP authentication, enter the CHAP user name and password. To enable Mutual CHAP, select and enter the Mutual CHAP user name and password.
Page 70
• Data Digest and Header Digest—Optionally, you can specify that a digest of data or header information be compiled during transmission to assist in troubleshooting. CHAP logon information—If CHAP authentication is required, • select this option and enter the Target secret. •...
Page 71
* * * An asterisk (*) represents the default value of a parameter. For example, your log on command might look like this: iscsicli PersistentLoginTarget iqn.1984- 05.com.dell:powervault.6001372000ffe3332xx0000046 72edf2 3260 T 192.168.130.101 * * * 0x2 * * * * * To view active sessions to the target, run the following command:...
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: Microsoft iSCSI Software Initiator 2.x User’s Guide See the for more information about the commands used in the previous steps. For more information about Windows Server 2008 Server Core, see the Microsoft Developers Network (MSDN) at microsoft.com.
Page 73
NOTE: Configure the management station you are using for network communication to the same IP subnet as the PowerVault MD36 0i host ports. 1 Establish an iSCSI session to the PowerVault MD3600i RAID storage array. 2 Restart the SMagent service. 3 Launch MDSM.