SAN P2000 & Clustering configuration

[p4c]

Hi,

We have to install a SAN P2000 on an Hyper-V cluster environement.

We have configure the following thing :

Two Serveurs on Windows 2008 R2 with 2 network card each (with 2 ports on each card)

Server 1 have  :

Administration card : 192.168.0.x / 255.255.255.0

Heartbeat network : 10.0.20.x / 255.255.255.0

ISCSI 1 : 10.0.0.10 / 255.255.0.0

ISCSI 2 : 10.0.0.11 / 255.0.0.0

 Server 2 have:

Administration card : 192.168.0.x / 255.255.255.0

Heartbeat network : 10.0.20.x / 255.255.255.0

ISCSI 1 : 10.0.0.21 / 255.255.0.0

ISCSI 2 : 10.0.0.22 / 255.0.0.0

SAN (HP P2000)

ISCSI A1 : 10.0.0.100 / 255.255.0.0 (ISCSI 1 Server 1 card is link to this interface)

ISCSI A2 : 10.0.0.101 / 255.255.0.0 (ISCSI 1 Server 2 card is link to this interface

ISCSI B1 : 10.0.0.102 / 255.0.0.0 (ISCSI 2 Server 1 card is link to this interface)

ISCSI B2 : 10.0.0.103 / 255.0.0.0 (ISCSI 2 Server 2 card is link to this interface)

ISCSI target are mounted on both server, quorum disk too as majority 

The only problem we have is that ISCSI 1 and ISCSI 2 Network card only communicate with the SAN (Direct Attached configuration)
But they cannot communicate each other. So Server 1 & 2 cannot communicate through their ISCSI 1 & 2 Network Card.

And that's a problem for a cluster environnment.

So, the question is : Is there a way to let ISCSI 1 & 2 Network card from each server to communicatate each other ? Maybe there is something to be done on the P2000 SAN ?

Thanks in advance,

Regards,

Maxime

IT Technician - WATSOFT 

[SUBHAJIT KHANBARMAN_1]

As per my understanding resource allocation is the Job of cluster service that you are running. It should take care of your iSCSI cards connectivity.

[Johan Guldmyr]

ISCSI 1 : 10.0.0.21 / 255.255.0.0
ISCSI 2 : 10.0.0.22 / 255.0.0.0

Why?
Why not
ISCSI 1 : 10.0.0.21 / 255.255.255.0
ISCSI 2 : 10.0.1.22 / 255.255.255.0

Do you not want the two iSCSI networks on two separate subnets? With the /8 subnet they are on the same "network" and you would need to use physical/vlan segmentation to separate the networks.

Anyway, why the /8 and /16 subnet difference?

I see that you want them on the same network. Then why not have the same netmask on all interfaces?

[p4c · Accepted solution]

Hi,

We have find a solution for this configuration. It was a misconfiguration on the Microsoft Cluster part.

Thanks