Professional Documents
Culture Documents
The ability to build a robust, fault-tolerant solution because an I/O path is built to every storage system in the cluster. For example, in a cluster with five storage systems, HP DSM for MPIO-connected volumes have six iSCSI MPIO connections to the SAN, one for each storage system and one for the administrative connection. Five of the six connections could go offline, and I/O would still be serviced.
The HP DSM for MPIO supports connecting multiple NICs in the application server to the SAN. Configuring with multiple NICs improves fault-tolerant physical network connections in the server. The HP DSM for MPIO can be used in a Multi-Site SAN with one or more subnets. In this configuration, the HP DSM for MPIO will only build I/O paths to the storage systems that are in the same subnet as the application server. Alternatively, you can assign an application server to a site. Application servers assigned to a site connect only to storage systems in the same site. Both of these configurations permit higher performance and lower network utilization by reducing the amount of I/Os that traverse the WAN link. NOTE: Refer to the instructions specific to Multi-Site SAN configurations in the rest of this chapter. You can also refer to the HP P4000 Multi-Site HA/DR Solution Pack User Guide, available on the HP P4000 Management Software DVD or on the HP P4000 Manuals page of the HP Business Support Center website. http://www.hp.com/support/manuals In the Storage section, navigate to Disk Storage SystemsP4000 SAN SolutionsHP LeftHand P4000 SAN Solutions or HP StorageWorks P4000 G2 SAN Solutions, depending upon your product.
Best Practices
If MPIO is not required, then do not install the HP DSM for MPIO or do not enable the the Microsoft MPIO service.
Description of the HP P4000 DSM for Microsoft MPIO 3
If currently using the HP DSM for MPIO, then upgrade to the latest version. Recommended uses for HP DSM for MPIO: For maximum possible performance for specified configurations. With Multi-Site SAN storage clusters, the HP DSM for MPIO with site preference is recommended, particularly if the inter-site link is significantly slower than local access. This configuration will ensure that reads are performed with a local replica when one is available. This is particularly useful for Microsoft clusters where a Microsoft cluster node is on each side of the inter-site link. For any volumes that are accessed by ESX and Windows initiators (as might be done for VMware Consolidated backup) do not use the HP DSM for MPIO. Large Hyper-V clusters (either large storage cluster or many server NICs). Large storage clusters with simultaneous access to many volumes using the HP DSM for MPIO may encounter the Microsoft limit of 255 iSCSI sessions. In this case, use Microsoft MPIO, which uses fewer sessions. To determine whether the Microsoft MPIO iSCSI session limit might apply, multiply the expected number of volumes by the number of storage systems plus the number of server NICs.
NOTE: If the storage configuration is not recommended for HP DSM for MPIO, then uninstall the HP DSM for MPIO during the upgrade to V9.x and use the Microsoft DSM.
NOTE: To help avoid issues with active/passive MPIO configurations (both the HP DSM for MPIO and Microsoft DSM) and disk timeout errors when the iSCSI initiator detect a failure and reconnects, you may want to change the EnableNOPOut registry setting to 1 as described in the Microsoft iSCSI Initiator Driver Timers section of the Microsoft iSCSI Software Initiator Version 2.X Users Guide.
Prerequisites
Windows Server 2003
32-bit or 64-bit version of Windows Server 2003 The latest Microsoft iSCSI Initiator Microsoft DSM installed
If you are running Version 8.0 or 8.1 of the HP DSM for MPIO, use the Solution Pack for Microsoft Windows DVD to upgrade to Version 9.0. After upgrading to Version 9.0, use the new installer provided in the HP P4000 Application Integration Solution Pack DVD.
From the Home page of HP P4000 Application Integration Solution Pack installer, click DSM for MPIO. From the HP P4000 DSM for Microsoft MPIO page, click Install DSM for MPIO to begin the installer. Accept the terms of the license agreement and click Next. The installation wizard takes you through the installation process for the HP DSM for MPIO. Reboot the server to complete the installation.
Perform a silent install for Windows Server 2008 Server Core option
1. 2. Open a command prompt and use the cd command to navigate to setup.exe in the installation media. Type the following command: setup /s /f1".\setup.iss"
Installing the HP DSM for MPIO 5
The setup begins. You will see nothing until after a minute or two, when the server reboots. 3. When the server is back up, check \Windows\dsminstall.log for errors.
6. 7. 8.
[Optional] If you want this volume to be available after rebooting, select the Automatically restore... check box. Click Advanced to open the Advanced Settings window. Configure the Advanced Settings as follows: For Local adaptor, select Microsoft iSCSI initiator. For Source IP, select the IP address of the storage NIC to connect to the volume. For Target portal, select the VIP of the cluster containing the volume.
9. Click OK to close the Advanced Settings dialog. 10. Click OK again to finish logging on. 1 If you want to set the MPIO load balancing policy, see Setting the Microsoft DSM MPIO load 1. balancing policy (page 8). 12. If you have multiple NICs, repeat steps 3 through 1 for the additional storage NICs. 1
In the HP DSM for MPIO, Vendor Specific is selected by default. This option is the same as selecting Fail Over Only and will not be available after you select another option. In the Microsoft DSM, Fail Over Only is the default selection for all Windows versions, except for Windows 2008 R2, for which Round Robin is the default. The MPIO load balancing policy affects the number of iSCSI connections created to the volume. The number of connections also differs based on whether you are using the HP DSM for MPIO or the Microsoft DSM. HP DSM for MPIO with two NICs in the server and Failover MPIO load balancing (page 8) through Microsoft DSM with two NICs in the server and Round Robin MPIO load balancing (page 9) show the connections created with applications servers that have two NICs. Figure 4 HP DSM for MPIO with two NICs in the server and Failover MPIO load balancing
Figure 5 HP DSM for MPIO with two NICs in the server and Round Robin MPIO load balancing
Figure 6 Microsoft DSM with two NICs in the server and Fail Over MPIO load balancing
Figure 7 Microsoft DSM with two NICs in the server and Round Robin MPIO load balancing
NOTE: Be sure to follow the steps below to set the MPIO load balancing policy. Similar options are available for Multiple Connected Session (Windows 2008) or Session Connections (Windows 2003). These session load balancing policies will have no effect. To set the MPIO load balancing policy: 1. Select the target you just logged on to and click Details. 2. Select the Devices tab. 3. Click Advanced. This step is not needed for Windows 2008 Server R2.
Connecting volumes with MPIO 9
4. 5. 6. 7.
Click the MPIO button or tab. If the MPIO button or tab is not available, MPIO is not installed and enabled. From the Load balancing policy drop-down list, select either Fail Over Only or Round Robin. Click OK. Click OK.
Troubleshooting MPIO
Verifying HP DSM for MPIO operations
After logging on to a volume via iSCSI, the HP DSM for MPIO automatically builds a data path to each storage system in the cluster and one administrative path. You can verify the HP DSM for MPIO operations by looking at the Details window of the iSCSI connection for the volume after logging on to that volume. Figure 8 Verifying the HP DSM for MPIO connections
10
Troubleshooting MPIO
When the problem with the I/O path is repaired, the HP DSM for MPIO reconnects an I/O path to the storage system, thus restoring optimized performance and fault tolerance.
1 1
Performing a silent uninstall for the Windows 2008 Server Core option
IMPORTANT: 1. 2. 3. 4. Uninstalling the HP DSM for MPIO requires a reboot of the system. Open a command prompt and use the cd command to navigate to setup.exe in the installation media. Type the following command: setup /removeonly /s /f1.\uninst.iss The uninstall begins. You will see nothing until after a minute or two, when the server reboots. When the server is back up, check \Windows\dsminstall.log for errors.
12