MSA Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

MSA 2050 Configuration in 3 Node 2016 Hyper-V Failover Cluster

 
SOLVED
Go to solution
Vint
Advisor

MSA 2050 Configuration in 3 Node 2016 Hyper-V Failover Cluster

Hello All,

I am building a 3 node Windows Server 2016 Datacenter Edition Failover cluster using DL380 G10 servers, an MSA 2050 (ISCSI with dual controllers). I have a pair of Aruba 2540 switches for the SAN. 

Switch 1 is configured as 192.168.3.3. Switch 2 is configured as 192.168.4.3.

Switch 1 has plugged into it MSA ports A1 (192.168.3.7) and B1 (192.168.3.8), as well as one network interface from each node, 192.168.3.4, 192.168.3.5, and 192.168.3.6.

Switch 2 has plugged into it MSA ports A2 (192.168.4.7) and B2 (192.168.4.8), as well as one network interace from each node, 192.168.4.4, 192.168.4.5, 192.168.4.6.

There is nothing else plugged into these switches, 5 ports total in use per switch.

My issue is that when I ping MSA Controller Ports B1 and A2, from all 3 nodes, I get Destination host unreachable.

 

Why is this? Does the MSA only respond on the "active" ports?

 

On the MSA, I have created a storage pool, created 4 volumes (1 witness and 3 CSVs). I have mapped one of the hosts to the volumes.

On the first Node, I have installed MPIO, configured ISCSI initiators, mapped the 4 volumes and they are formatting now.

 

Thanks,

Vintr

1 REPLY 1
Vint
Advisor
Solution

Re: MSA 2050 Configuration in 3 Node 2016 Hyper-V Failover Cluster

This was totally self inflicted. 

 

I got my wires crossed between the switches and the MSA.

 

All is well.

 

Thanks,

Vint