book.
book.book Page 2 Thursday, July 18, 2013 5:39 PM Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer. CAUTION: A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. ___________________ © 2013 Dell Inc.
book.book Page 3 Thursday, July 18, 2013 5:39 PM Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . System Requirements . . . . . . . . . . . . . . . . . . . 2 Hardware Installation 7 . . . . . . . . . . . . . . 8 . . . . . . . . . . . . . . . Planning the Storage Configuration . 11 . . . . . . . . . . . . . 12 . . . . . . . . . . . . . . . 12 . 12 . . . . . . . . . . 13 Redundant and Non-Redundant Configurations .
book.book Page 4 Thursday, July 18, 2013 5:39 PM Console Installation . Silent Installation . . . . . . . . . . . . . . . . 34 . . . . . . . . . . . . . . . . . . 34 Upgrading MD Storage Software 4 Post Installation Tasks . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 . . . . . . . . . . . . . 38 IPv4 Settings—Worksheet . . . . . . . . . . . . . 39 IPv6 Settings—Worksheet . . . . . . . . . . . . . 40 . . . . . . . .
book.book Page 5 Thursday, July 18, 2013 5:39 PM 5 Uninstalling MD Storage Software . . . . . Uninstalling MD Storage Software From Windows . . 51 . . . . 52 . . . . . . . . . . . . . . . . . . . . . . 53 Uninstalling MD Storage Software From Linux . 6 Getting Help . 51 Locating Your System Service Tag Contacting Dell . . . . . . . . . . . 53 . . . . . . . . . . . . . . . . . . . . . 53 Documentation Feedback . . . . . . . . . . . . . . . . A Appendix—Manual Configuration of iSCSI . .
book.book Page 6 Thursday, July 18, 2013 5:39 PM CHAP Definitions . . . . . . . . . . . . . . . . . . Step 5: Configure CHAP Authentication on the Storage Array (Optional) . . . . . . . . . . . . . . . . . Configuring Target CHAP Authentication on the Storage Array . . . . . . . . . . . . . . . . . . Configuring Mutual CHAP Authentication on the Storage Array . . . . . . . . . . . . . . . 65 66 . . . . . 67 . . . . . . 71 Step 8: (Optional) Set Up In-Band Management. . . . .
book.book Page 7 Thursday, July 18, 2013 5:39 PM 1 Introduction This guide provides information about deploying Dell PowerVault MD3600i and Dell PowerVault MD3620i storage arrays. The deployment process includes: • Hardware installation • Modular Disk Storage Manager (MDSM) software installation • Initial system configuration Other information provided include system requirements, storage array organization, and utilities. NOTE: For more information on product documentation, see dell.
book.book Page 8 Thursday, July 18, 2013 5:39 PM • Display resolution of 1024x768 with 16 million colors (1280x1024 32-bit recommended). • Microsoft Windows, Red Hat Enterprise Linux, or SUSE Linux Enterprise Server. NOTE: Supported operating systems include both native and guest operating systems. NOTE: Supported hypervisors include Microsoft Hyper-V, Citrix XenServer, and VMware. For information about the supported versions, see the Support Matrix at dell.com/support.
book.book Page 9 Thursday, July 18, 2013 5:39 PM Unconfigured capacity comprises 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 is not assigned to any virtual disk. Data is written to the physical disks in the storage array using RAID technology.
book.
book.book Page 11 Thursday, July 18, 2013 5:39 PM 2 Hardware Installation 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. • 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.
book.book Page 12 Thursday, July 18, 2013 5:39 PM Connecting the Storage Array The storage array is connected to a host using two hot-swappable RAID controller modules. The RAID controller modules are identified as RAID controller module 0 and RAID controller module 1. Each RAID controller module has two iSCSI In port connectors that provide Ethernet connections to the host server or switches. Each RAID controller module also contains an Ethernet management port and a SAS Out port.
book.book Page 13 Thursday, July 18, 2013 5:39 PM Direct-Attached Configurations You can connect the Ethernet ports of the host servers directly to the storage array RAID controller module iSCSI ports. Single Path Data Configurations With a single path configuration, a group of heterogeneous hosts can be connected to the storage array through a single physical Ethernet port. Since there is only one port, there is no redundancy, although each iSCSI portal supports multiple connections.
book.book Page 14 Thursday, July 18, 2013 5:39 PM Figure 2-1 shows a non-redundant cabling configuration to the RAID controller modules using a single path data configuration. Figure 2-1.
book.book Page 15 Thursday, July 18, 2013 5:39 PM Figure 2-2 shows one host connected to a single controller array. Figure 2-2.
book.book Page 16 Thursday, July 18, 2013 5:39 PM Figure 2-3 shows four stand-alone hosts supported in a dual controller array configuration with a single data path. Figure 2-3.
book.book Page 17 Thursday, July 18, 2013 5:39 PM Dual Path Data Configuration In Figure 2-4, 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.
book.book Page 18 Thursday, July 18, 2013 5:39 PM Figure 2-4.
book.book Page 19 Thursday, July 18, 2013 5:39 PM Figure 2-5.
book.book Page 20 Thursday, July 18, 2013 5:39 PM Network-Attached Configurations You can also cable the host servers to the RAID controller module iSCSI ports through industry-standard 10G or 1G Ethernet switches. An iSCSI configuration that uses Ethernet switches is frequently referred to as an IP SAN. By using an IP SAN, the PowerVault MD3600i series storage array can support up to 64 hosts simultaneously.
book.book Page 21 Thursday, July 18, 2013 5:39 PM Figure 2-6.
book.book Page 22 Thursday, July 18, 2013 5:39 PM Figure 2-7.
book.book Page 23 Thursday, July 18, 2013 5:39 PM Figure 2-8.
book.book Page 24 Thursday, July 18, 2013 5:39 PM Figure 2-9.
book.book Page 25 Thursday, July 18, 2013 5:39 PM Cabling PowerVault MD1200 Series Expansion Enclosures You can expand the capacity of your PowerVault MD3600i series storage array by adding PowerVault MD1200 series expansion enclosures. You can expand the physical disk pool to a maximum of 120 (or 192, if enabled using Premium Feature activation) physical disks using a maximum of seven expansion enclosures.
book.book Page 26 Thursday, July 18, 2013 5:39 PM a Install the software and driver package included on the PowerVault MD series resource media. For information about installing the software, see "Installing PowerVault MD Storage Software" on page 31. b Update the storage array RAID controller module firmware and NVSRAM to the latest versions available at dell.com/support, using MDSM. c Click Tools Upgrade RAID Controller Module Firmware in the Enterprise Management Window (EMW).
book.book Page 27 Thursday, July 18, 2013 5:39 PM Expanding With New PowerVault MD1200 Series Expansion Enclosures Perform the following steps to attach new PowerVault MD1200 series expansion enclosures to a PowerVault MD3600i series storage array: 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.
book.book Page 28 Thursday, July 18, 2013 5:39 PM c • If the status LEDs are solid amber, the storage array 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 are solid blue, the storage array is ready. After the storage array is online and ready, turn on any attached host systems.
book.
book.
book.book Page 31 Thursday, July 18, 2013 5:39 PM 3 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 Linux and Windows operating systems. The readme.
book.book Page 32 Thursday, July 18, 2013 5:39 PM NOTE: If Dynamic Host Configuration Protocol (DHCP) is not used, initial configuration of 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 port (192.168.128.101 or 192.168.128.102).
book.book Page 33 Thursday, July 18, 2013 5:39 PM 2 Select Install MD Storage Software. 3 Read and accept the license agreement. 4 Select one of the following installation options from the Install Set dropdown menu: • Full (recommended)—Installs the MD Storage Manager (client) software, host-based storage agent, multipath driver, and hardware providers. • Host Only—Installs the host-based storage agent and multipath drivers. • Management—Installs the management software and hardware providers.
book.book Page 34 Thursday, July 18, 2013 5:39 PM NOTE: 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. In addition, see the Support Matrix at dell.com/support/manuals for any additional settings and/or software required for your specific storage array.
book.book Page 35 Thursday, July 18, 2013 5:39 PM 2 Modify the custom_silent.properties file to reflect the features, models and installation options to be used. Then, save the file. 3 Once the custom_silent.properties file is revised, run the following command to begin the installation: ./mdss_install.bin –f /custom_silent.
book.
book.book Page 37 Thursday, July 18, 2013 5:39 PM Post Installation Tasks 4 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.
book.book Page 38 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 39 Thursday, July 18, 2013 5:39 PM IPv4 Settings—Worksheet host server A 192.168.131.101 (In 1 default) 192.168.130.101 (In 0 default) B Mutual CHAP Secret 192.168.128.101 (management network port) Target CHAP Secret PowerVault MD36x0i 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.
book.book Page 40 Thursday, July 18, 2013 5:39 PM IPv6 Settings—Worksheet Host server A Mutual CHAP Target CHAP B PowerVault MD36x0i If you need additional space for more than one host server, use an additional sheet. A B Link local IP address ___ . ___ . ___ . ___ Host iSCSI port 2 Link local IP address ___ . ___ . ___ . ___ Routable IP address ___ . ___ . ___ . ___ Routable IP address ___ . ___ . ___ . ___ Subnet prefix ___ . ___ . ___ . ___ Subnet prefix ___ . ___ . ___ .
book.
book.book Page 42 Thursday, July 18, 2013 5:39 PM Configuring iSCSI on Your Storage Array The following sections contain step-by-step instructions for configuring iSCSI on your storage array. However, before you begin, it is important to understand where each of these steps occur in relation to your host server or storage array environment. The following table shows each iSCSI configuration step and where it occurs. Table 4-2. Host Server Vs.
book.book Page 43 Thursday, July 18, 2013 5:39 PM Automatic Configuration Using the Modular Disk Configuration Utility NOTE: If MDCU is not installed, it can be installed from the MD series resource media. The MDCU provides a consolidated approach for configuring the iSCSI network of host servers and iSCSI-based storage arrays using a wizard-driven interface.
book.book Page 44 Thursday, July 18, 2013 5:39 PM 7 Apply the settings after reviewing a summary. 8 Repeat the process starting from step 2 to configure additional arrays. Host Configuration (Host Connectivity Configuration) After you have completed configuring your iSCSI-based storage arrays, the next task is to run this utility on all hosts that need to access the storage arrays.
book.book Page 45 Thursday, July 18, 2013 5:39 PM • 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.
book.book Page 46 Thursday, July 18, 2013 5:39 PM 8 Verify that communication is established between the storage array and host server. NOTE: For more information on MDCU, see the MDCU online help. Post Connection Establishment Steps After iSCSI connectivity is established between the host server(s) and the storage array, you can create virtual disks on the storage array using MD Storage Manager and these virtual disks can be utilized by the host server(s).
book.book Page 47 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 48 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 49 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 50 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 51 Thursday, July 18, 2013 5:39 PM 5 Uninstalling MD Storage Software Uninstalling MD Storage Software From Windows Use the Change/Remove Program feature to uninstall the Dell PowerVault Modular Disk Storage Software (MDSS) from Microsoft Windows operating systems other than Microsoft Windows Server 2008: 1 From the Control Panel, double-click Add or Remove Programs. 2 Select Dell MD36xxi Storage Software from the list of programs. 3 Click Change/Remove.
book.book Page 52 Thursday, July 18, 2013 5:39 PM 2 From the installation directory, type the following command and press : Uninstall Dell MD Storage Software 3 From the Uninstall window, click Next and follow the instructions on the screen. 4 Select Yes to restart the system, then click Done. Uninstalling MD Storage Software From Linux 1 By default, MD Storage Manager is installed in the /opt/dell/mdstoragemanager directory.
book.book Page 53 Thursday, July 18, 2013 5:39 PM 6 Getting Help Locating Your System Service Tag Your system is identified by a unique Express Service Code and Service Tag number. The Express Service Code and Service Tag are found on the front of the system by pulling out the information tag. This information is used by Dell to route support calls to the appropriate personnel. Contacting Dell NOTE: Dell provides several online and telephone-based support and service options.
book.book Page 54 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 55 Thursday, July 18, 2013 5:39 PM A 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 A-1 shows each iSCSI configuration step and where it occurs. Table A-1. Host Server Vs.
book.book Page 56 Thursday, July 18, 2013 5:39 PM 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. The default IP configuration is: Controller 0: 255.255.255.
book.book Page 57 Thursday, July 18, 2013 5:39 PM 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 74. You can discover the storage array either automatically or manually. Select one and complete the following procedure.
book.book Page 58 Thursday, July 18, 2013 5:39 PM After discovery is complete, a confirmation screen is displayed. 3 Click Close to close the screen. Manual Storage Array Discovery 1 Launch MDSM. If this is the first storage array to be set up, the Add New Storage Array window is displayed. 2 Select Manual and click OK. 3 Select Out-of-band management and enter the host server name(s) or IP address(es) of the iSCSI storage array controller. 4 Click Add.
book.book Page 59 Thursday, July 18, 2013 5:39 PM Table A-2. Initial Setup Tasks Dialog Box 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. MDSM may ask for a password before changing the configuration or performing a destructive operation.
book.book Page 60 Thursday, July 18, 2013 5:39 PM 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. 3 Configure the iSCSI ports on the storage array.
book.book Page 61 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 62 Thursday, July 18, 2013 5:39 PM • 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 \\ config msiscsi start=auto 2 Start the iSCSI service: sc start msiscsi 3 Add a target portal: iscsicli QAddTargetPortal If you are using Red Hat Enterprise Linux
book.book Page 63 Thursday, July 18, 2013 5:39 PM 5 To display the available iSCSI targets at the specified IP address, use the following command: iscsiadm –m discovery –t st -p 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.
book.book Page 64 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 65 Thursday, July 18, 2013 5:39 PM CHAP Definitions To summarize the differences between target CHAP and mutual CHAP authentication, see Table A-3. Table A-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.
book.book Page 66 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 67 Thursday, July 18, 2013 5:39 PM 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 65, complete the following steps. If not, skip to "Step 7: Connect to the Target Storage Array From the Host Server" on page 71. Select the set of steps in one of the following sections (Windows or Linux) that corresponds to your operating system.
book.book Page 68 Thursday, July 18, 2013 5:39 PM • 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. NOTE: If the connection fails, ensure that all IP addresses are entered correctly.
book.book Page 69 Thursday, July 18, 2013 5:39 PM 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 = node.session.auth.
book.book Page 70 Thursday, July 18, 2013 5:39 PM 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.200503.com.redhat01.78b1b8cad821 node.session.auth.password = password_1 node.session.auth.username_in= iqn.198405.com.dell:powervault.123456 node.session.auth.password_in = test1234567890 discovery.sendtargets.auth.authmethod = CHAP discovery.sendtargets.auth.username = iqn.200503.com.
book.book Page 71 Thursday, July 18, 2013 5:39 PM 7 Select one: • If you are not using CHAP authentication, select No Authentication. Go to step 8. or • 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. 8 Repeat step 7 for each target until at least one connection is logged in for each controller. 9 Go to Connected Targets. 10 Verify that the targets are connected and displays a status of true.
book.book Page 72 Thursday, July 18, 2013 5:39 PM • 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. • Perform mutual authentication—If mutual CHAP authentication is configured, select this option. NOTE: IPSec is not supported. 7 Click OK.
book.book Page 73 Thursday, July 18, 2013 5:39 PM 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.
book.book Page 74 Thursday, July 18, 2013 5:39 PM 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. For more information about Windows Server 2008 Server Core, see the Microsoft Developers Network (MSDN) at microsoft.com.
book.book Page 75 Thursday, July 18, 2013 5:39 PM NOTE: Configure the management station you are using for network communication to the same IP subnet as the PowerVault MD36x0i host ports. 1 Establish an iSCSI session to the PowerVault MD3600i RAID storage array. 2 Restart the SMagent service. 3 Launch MDSM. If this is the first storage array to be set up for management, the Add New Storage Array window is displayed. Otherwise, click New. 4 Select Manual and click OK.
book.
book.book Page 77 Thursday, July 18, 2013 5:39 PM B Appendix—Using Internet Storage Naming Service 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.
book.
book.book Page 79 Thursday, July 18, 2013 5:39 PM Appendix—Load Balancing C 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.
book.book Page 80 Thursday, July 18, 2013 5:39 PM Least Queue Depth With Subset The least queue depth with subset policy is also known as the least I/Os or least requests policy. This policy routes the next I/O request to a data path that has the least outstanding I/O requests queued. For this policy, an I/O request is simply a command in the queue. The type of command or the number of blocks that are associated with the command are not considered.
book.book Page 81 Thursday, July 18, 2013 5:39 PM To change the load balance policy using Windows Server 2008 disk management: 1 From the desktop of the host, right-click My Computer and click Manage to open the Computer Management dialog box. 2 Click Disk Management to show the list of virtual disks attached to the host. 3 Right-click the virtual disk for which you want to set the load balance policy, then click Properties.
book.book Page 82 Thursday, July 18, 2013 5:39 PM Figure C-1.
book.book Page 83 Thursday, July 18, 2013 5:39 PM Two sessions with one TCP connection are configured from the host to each controller (one session per port), for a total of two 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.
book.
book.book Page 85 Thursday, July 18, 2013 5:39 PM Appendix—Stopping iSCSI Services in Linux D Follow the procedure given below to manually stop the iSCSI services in Linux. To shut down iSCSI services: 1 Stop all I/O. 2 Unmount all correlated file systems. Stop iSCSI services by running the following command: /etc/init.
book.
