ip configuration for 2node converged cluster
Posted: Mon Aug 18, 2014 8:58 am
Hi there!
I've got a question about where to use which IP address, and what it might affect. (sounds very simple, but i haven't understood it right how starwind handles it)
I'm rebuilding my home lab, consisting of 2 nodes(with starwind and Hyper-v on them) and I'm a little confused.
Here are my Networks:
- 10Gbit/s Sync / Heatbeat - 172.17.1.0 - Point 2 Point
- 10Gbit/s Migration(Hyper-V) / Heartbeat - 172.17.2.0 - Point 2 Point
- ~2Gbit/s 192.168.1.0 - Client Network / Heartbeat (LACP-Trunk with a VLAN-Trunk, Client network is one VLAN, IP addresses from here are listed in DNS)
- couple of other vlans that don't play a role here
what i'd like to get / build is that vms running on node a access the storage within node a, only changes get synced.
on node a crash, i'd expect the failovercluster booting my machines on node b, accessing the storage on node b.
IF the attached storage of node a fails, vms should stay on node a and use storage from node b accessing it over one of the 10gbit links.
and only looking at those 2 machines, i don't like to access any storage using 1gbit links.
(maybe i'll create an additional vlan for iscsi later, if i want to connect other servers to that storage, but not needed now)
Now... I'm unsure which IP addresses to use when:
a) adding them to the management console (does this affect anything?e.g. like the address that gets used if i click on "connect storage on the servers")
- if i use one of the addresses of the 10Gbits there will be problems if the partner node is down, as the local port also becomes down (point 2 point), and therefore the 172.17. network is unreachable)
- if i use the client network to add them(192.168.1.0)
- if i use loopback ( the local server is already listed as 127.0.0.1...)
b) when creating the cluster via "create new cluster"
- is it even a good idea to have node a and b listed under servers, and also under servers residing under Clusters.
c) adding them to the iscsi initiator
- should i use loopback and 172. something? on node a and b?
I would be very glad if someone could explain this to me, as i'm a bit unsure what i'm doing here...(and honestly: I don't like to try and error this)
Kind regards!
I've got a question about where to use which IP address, and what it might affect. (sounds very simple, but i haven't understood it right how starwind handles it)
I'm rebuilding my home lab, consisting of 2 nodes(with starwind and Hyper-v on them) and I'm a little confused.
Here are my Networks:
- 10Gbit/s Sync / Heatbeat - 172.17.1.0 - Point 2 Point
- 10Gbit/s Migration(Hyper-V) / Heartbeat - 172.17.2.0 - Point 2 Point
- ~2Gbit/s 192.168.1.0 - Client Network / Heartbeat (LACP-Trunk with a VLAN-Trunk, Client network is one VLAN, IP addresses from here are listed in DNS)
- couple of other vlans that don't play a role here
what i'd like to get / build is that vms running on node a access the storage within node a, only changes get synced.
on node a crash, i'd expect the failovercluster booting my machines on node b, accessing the storage on node b.
IF the attached storage of node a fails, vms should stay on node a and use storage from node b accessing it over one of the 10gbit links.
and only looking at those 2 machines, i don't like to access any storage using 1gbit links.
(maybe i'll create an additional vlan for iscsi later, if i want to connect other servers to that storage, but not needed now)
Now... I'm unsure which IP addresses to use when:
a) adding them to the management console (does this affect anything?e.g. like the address that gets used if i click on "connect storage on the servers")
- if i use one of the addresses of the 10Gbits there will be problems if the partner node is down, as the local port also becomes down (point 2 point), and therefore the 172.17. network is unreachable)
- if i use the client network to add them(192.168.1.0)
- if i use loopback ( the local server is already listed as 127.0.0.1...)
b) when creating the cluster via "create new cluster"
- is it even a good idea to have node a and b listed under servers, and also under servers residing under Clusters.
c) adding them to the iscsi initiator
- should i use loopback and 172. something? on node a and b?
I would be very glad if someone could explain this to me, as i'm a bit unsure what i'm doing here...(and honestly: I don't like to try and error this)
Kind regards!