«

»

Jun 22

Windows Server Failover Clustering Setup – Corrections

After the warts and all video that was in the last post I went away and started correcting the warnings that came up.

 

Dell MD300i SAN

After some more research I changed the configuration of our SAN and iSCSI network. The SAN has 2 controllers each with 2 iSCSI ports, I setup the IP addresses as shown below

  • Module 0, Port 0 – 192.168.1.10/24
  • Module 0, Port 1 – 192.168.1.11/24
  • Module 1, Port 0 – 192.168.2.10/24
  • Module 1, Port 1 – 192.168.2.11/24

I then setup each server to have 2 network cards associated with the iSCSI network, 1 on each of the subnets from the SAN settings. Then I setup 2 switches, 1 for each subnet and connected them up appropriately

 

MPIO

On investigation into the errors about MPIO I found that Dell recommend using their configuration utility to setup the iSCSI initiator on Windows. So armed with DVD, I deleted all references to the SAN in the iSCSI setup and ran the Dell config utility and sure enough it added all the necessary settings into the iSCSI initiator

Network

The warnings on the network mainly consisted of multiple network cards on the same subnet. Part of this was resolved by have the iSCSI cards on different subnets but the rest were obviously on the same subnet because they were setup for Hyper-V. I did some more research and found that in Hyper-V manager you can set it so that Hyper-V and the actual server don’t share the network card.

a

So after changing all these settings I ran the validation tool again. The next series of screens shows the output.

 

1

2

3

4

As you can see the only warnings I get now are about there being no default gateway setup and as this is very much a test bed we can ignore that warning.

So with all the warnings sorted the cluster was created in exactly the same way as the last video post. The next videos will be about setting up a highly available virtual machine and a demo of the live migration feature.

Leave a Reply