I am trying to setup a simple environment (virtual) to prove that when a Node in a cluster goes down, the other picks up.
After much pain I think I may have this however I would love for people here to see if I have setup the system correctly?
I want to make sure that for example, the disks are correctly configured. It’s a simple 2 Node cluster on WS2008 R2.
Configuration
DC
1 Private NIC
IP: 192.168.1.2
Sub: 255.255.255.0
DNS Server: 127.0.0.1
Node 1
2 NICs. 1 NIC is a public nic.
Private Nic 1:
IP: 192.168.1.3
Sub: 255.255.255.0
Gateway: 192.168.106.1 <– this is a VMWare thing I believe
DNS: 192.168.1.2
Node2
2 NICs. 1 NIC is a public nic.
Private Nic 1:
IP: 192.168.1.4
Sub: 255.255.255.0
Gateway: 192.168.106.1 <– this is a VMWare thing I believe
DNS: 192.168.1.2
VSAN
So I am using Starwind to create iSCSI storage/targets on this virtual machine. Oh – I dont have much clue about iSCSI!
VSAN IP: 192.168.1.5
Sub: 255.255.255.0
Gateway: 192.168.106.1
DNS: 192.168.1.2
I have 4 targets here.
Clustering Info
There are 2 nodes in this cluster, as you gathered from above.
ClusterIP: 192.168.1.16
ClusterName: w2k8r2-clstr
Now, in regards to the disks, I see them as different volumes.
Cluster Disk 1 is a Witness in Quorum
Available Storage: Cluster Disk 2, 3, 4
I see that if I reboot Node 1, the disks appear in my computer on Node 2
If Node 2 is rebooted, I see the disks appear in my computer on Node 1
is this the correct behavior? Have I missed something? wrong configuration?
Thats all for now. I REALLY hope someone can help, I would appreciate it 
Your networking is quite messed up, and you don’t tell anything about your private NIC configuration, but I’ll give it a try.
First of all, you can’t use a default gateway of 192.168.106.1 on a computer which is connected to the 192.168.1.0/24 network; there’s just no way that computer could actually reach the gateway. If VMware has automatically configured your virtual network to use the 192.168.106.0/24 subnet, you need to either stick to it or configure it to use the same subnet you want to use for your VMs (192.168.1.0/24). For the sake of simplicity, let’s just assume you don’t change anything: then, your main network should use the 192.168.106.0/24 subnet, and your virtual servers should be configured accordingly.
Then there’s the iSCSI setup; while it is possible to run iSCSI on the same network used for public cluster access, this is definitely not a proper setup; you should use a dedicated network for iSCSI. You aren’t saying where you are actually running your StarWind software, but chances are you are running it in another VM. You should add another NIC to that VM and to the two cluster nodes, and use those NICs for iSCSI (BTW, if it’s a Windows Server 2008 R2 VM, you don’t need the StarWind software: Microsoft offers a free iSCSI target software for this system; see here). You should configure your iSCSI target software to offer its services on the iSCSI IP address, and then configure the cluster nodes to use that IP address as their iSCSI target.
Finally, you are mixing the terms “private” and “public” here; in cluster terminology, the “public” network is the one through which flows all communications between the nodes and the rest of the world, while the “private” one is only for the cluster nodes to talk between themselves. This means the DC should be on the “public” network, not on the “private” one.
Your setup should include three networks (public, private and iSCSI); as I said above, the main network should use the same subnet where your default gateway resides; you are free to choose any other subnet for the other two networks.
In this example, I’ll use the following networks:
Public: 192.168.106.0/24
Private: 192.168.10.0/24
iSCSI: 192.168.20.0/24
Your setup should look like this:
DC:
1 NIC, public network: 192.168.106.2/24, DNS 192.168.106.2, default gateway 192.168.106.1
iSCSI Server:
1 NIC, public network: 192.168.106.5/24, DNS 192.168.106.2, default gateway 192.168.106.1
1 NIC, iSCSI network: 192.168.20.5/24, no DNS, no default gateway
Node 1:
1 NIC, public network: 192.168.106.3/24, DNS 192.168.106.2, default gateway 192.168.106.1
1 NIC, private network: 192.168.10.3/24, no DNS, no default gateway
1 NIC, iSCSI network: 192.168.20.3/24, no DNS, no default gateway
Node 2:
1 NIC, public network: 192.168.106.4/24, DNS 192.168.106.2, default gateway 192.168.106.1
1 NIC, private network: 192.168.10.4/24, no DNS, no default gateway
1 NIC, iSCSI network: 192.168.20.4/24, no DNS, no default gateway
Check more discussion of this question.