Setting Up MPIO for a Windows Cluster Using a Storage System
Configuration
The components in this configuration are:
Two server hosts
Two Server hosts -exhost1, exhost2 - running:
- Windows Server 2008 R2
- Microsoft iSCSI Initiator 2.08
- Failover Clustering
- Multipath I/O
One storage system
One storage system configured as follows:
- Two iSCSI interfaces (iscsia, iscsib) configured as described in the table below.
Note: The second iSCSI interface is optional.
Table 1. Storage System iSCSI interface configuration NameDetailsiscsia- IP addresses: 11.222.123.156, 11.222.224.231
- Target: IQN.192-05.com.emc: fcnev1005000720000-1
- Storage processor: SP A
- Ethernet interface: eth3, et2
iscsib- IP addresses: 11.222.123.157, 11.222.224.232
- Target: IQN.192-05.com.emc: fcnev1005000720000-2
- Storage processor: SP B
- Ethernet interface: eth3, et2
- iSCSI storage resources:
- cluster_disk1 (Quorum disk, which is optional, though recommended, for Windows Server 2008 R2)
- cluster_disk2 (optional)
- cluster_disk3 (optional)
The following figure shows how these components are networked together.
Figure 1. Network configuration
Setting up cluster nodes (hosts)
Configure the iSCSI initiator with MPIO on each cluster node
- In the Microsoft iSCSI Initiator, select , add the target portal IP address or the DNS name.
- Select Advanced Settings dialog box set the following for both the primary and secondary local adapters:
and in the
- Local adapter to Microsoft iSCSI Initiator.
- Initiator IP to the IP address for the local adapter interface on subnet 11.222.123.xxx for the primary local adapter, and to 11.222.224.xxx for the secondary local adapter.
The host will look for targets on the following portals:
AddressPortAdapterIP address11.222.123.1563260Microsoft iSCSI Initiator11.222.123.xxx11.222.224.2313260Microsoft iSCSI Initiator11.222.224.xxx
- Select
, select the following in the Connect to Target dialog box:
- Add this connection to the list of Favorites
- Enable multi-path (ensure the Windows MPIO feature is installed first)
- Select Advanced Settings dialog box, set the following:
and in the
- Local adapter to Microsoft iSCSI Initiator.
- Initiator IP to the IP address for the local adapter interface on subnet 11.222.123.xxx.
- Target portal IP to 11.222.123.156 / 3260.
- Add the secondary session to the existing connection for MPIO:
- Select .
- In the Advanced Settings dialog box, set the following:
- Local adapter to Microsoft iSCSI Initiator.
- Initiator IP to the IP address for the local adapter interface on subnet 11.222.124.xxx.
- Target portal IP to 11.222.224.231 / 3260.
Enable MPIO on each cluster node
- Click Start and enter MPIO to launch the control panel applet.
- Click the Discover Multi-Path tab, select Add support for iSCSI devices, and click Add.
- Reboot the node when prompted to do so.
Verify the MPIO settings on each cluster node
- After the node finishes rebooting, go to
and verify that the MPIO hardware IDs (MSInitiator) for the storage system devices were added. Note: Device Hardware ID MSFT2005iSCSIBusType_0x9 adds support for all iSCSI devices.
- Verify the MPIO settings in the Microsoft iSCSI Initiator:
- In the Targets tab, select the storage system target and click Properties.
- In the Sessions tab, select the identifier for the session, click Devices.
- In the Devices tab, for each storage device (cluster_disk1, cluster_disk2, cluster_disk3), do the following:
- Select the device and click MPIO.
- In the MPIO tab, select the first connection, click Connections, and verify the following:
Source PortalTarget Portal11.222.123.123/xxxx11.222.123.156/3260
- In the MPIO tab, select the second connection, click Connections, and verify the following:
Source PortalTarget Portal11.222.123.224/yyyy11.222.224.231/3260
Present the storage devices to the Primary Node in the cluster
On the Primary Node in the cluster (exhost1), format each storage device (cluster_disk1, cluster_disk2, cluster_disk3) and assign a respective letter to each partition. In this example, E is assigned to cluster_disk1_ quorum; F is assigned to cluster_disk2; and, G is assigned to cluster_disk3.
Configure the cluster configuration on the Primary Node
The steps below follow Microsoft’s best practices for clusters.
On the Primary Node (exhost1), in Failover Cluster Manager:
- Select
and create an Access Point for administering the cluster and choose the static cluster IP.
For example:
- Domain: app.com
- Node 1: exhost1.app.com
- Node 2: exhost2.app.com
- Cluster Name: ex_cluster1.app.com
- Network: 11.222.224.0/xx with address 11.222.224.yyy
- Configure the network settings:
- Select the cluster (ex_cluster1).
- Select
(Cluster Network 3) with the following default settings:
- Allow cluster network communications on this network
- Allow clients to connect through this network
- Select
(Cluster Network 1) with the following default settings:
- Do not allow cluster network communication on this network
- Select
(Cluster Network 2) with the following default settings:
- Do not allow cluster network communication on this network
- Verify dependencies:
- Select the cluster (ex_cluster1).
- Click Cluster Core Resources and verify the following:
- In the cluster’s Name:ex_cluster1 Properties dialog box, verify that the dependencies are IP address (11.22.224.x) AND cluster_disk1.
- In the cluster’s IP Address: 11.222.224.x Properties dialog box, verify that the dependencies is cluster_disk1.
Note: The Cluster Disk Witness should always be the Quorum disk cluster_disk1, which is the default setting, but it can be changed.