Hello,
I have 2 HP servers and an HP MSA. The goal here is to cluster these 2 machines together and have them share the MSA storage for use with SQL server. The HP MSA has dual controllers so it connected to each server twice using crossover cables. The current configuration has both server connected to a management switch, as well as the management port on the MSA.
Each server is then connected to each iSCSI controller on the MSA via a crossover.
Server1:
management 172.16.100.1
MSA A110.0.0.1
MSA B110.0.0.3
Server2:
management 172.16.100.2
MSA A210.0.0.2
MSA B210.0.0.4
MSA:
management 172.16.100.3/172.16.100.4
A110.0.0.11A210.0.0.12
B110.0.0.13B210.0.0.14
I then created an iSCSI connection from each server to the MSA using both MSA addressed. So Server1 can discover the MSA using 10.0.0.11 or 10.0.0.13. After I made these connections and configured the disks I enabled windows cluster fail over. After putting both servers into the fail over cluster I was able to get past almost ALL validation checks besides it complaining that A1 NIC can not ping B1 NIC. An obvious issue due to them being isolated crossover networks. I confirmed that my cluster was functioning and even tested the disk fail over multiple times. When Server1 goes down Server2 is than the owner of all the data on the MSA. GREAT.
Now that I have explained the architecture our goal is to install SQL 2014 on these machines and use the MSA storage for the database so it can have a cold/hot backup. While this configuration would lose some data it would be minimal during fail over.
The problem is when installing SQL in a fail over configuration it re-runs the cluster validation and fails it due to these networks not being able to communicate. I have tried Teaming the NIC's together with no great outcome. I am really stuck as to how to get past this validation section. Most online instructions everyone is using this WSFC for virtual machines when we really just want to use it to share storage.
Thanks for any and all help I truly appreciate it.