HELLO MICROSOFT
i hope to fix cluster configuration in next windows server version stable... to be easy setup and more clear.
I spend a week to figure cluster communication network between two nodes servers.. here is my case study to see if i can get answer to my questions.
I do different Scenarios for bellow two node in real physical hardware and virtualization to be manage storage in PowerEdge 430r both nodes
NODE#1
SERVER NAME: CLUSTER-A
OS: WINDOWS SERVER 2019 DATACENTER
NIC1: 192.168.2.1 as Management (Mgmt)
NIC2: 172.16.1.1 as (SMB01)
NIC3: 172.16.2.1 as (SMB02)
NIC4: 192.168.1.1 as Internet
NODE#2
SERVER NAME: CLUSTER-B
OS: WINDOWS SERVER 2019 DATACENTER
NIC1: 192.168.2.200 as Management (Mgmt)
NIC2: 172.16.1.2 as (SMB01)
NIC3: 172.16.2.2 as (SMB02)
NIC4: 192.168.1.200 as Internet
_________
Scenario#1
_________
1- Connect both nodes (CLUSTER-A,CLUSTER-B) in >>real physical switch<<between CLUSTER-A NIC1 and CLUSTER-B NIC1
2- Install hyper-v and other cluster features tools in both nodes.
3- create virtual switch(Mgmt) and virtual switch (Internet) in both CLUSTER-A,CLUSTER-B.
4- create virtual primary domain server in CLUSTER-A and virtual secondary domain server in CLUSTER-B.
5- connect both virtual domains by virtual switch(Mgmt) and virtual switch (Internet).
6- restart both and be sure they are working fine.
7- create virtual GATEWAY server inside CLUSTER-A and create other in CLUSTER-B to manage nodes in future and connected with virtual (Mgmt) and virtual Internet.
8- NOW.. direct connect CLUSTER-A NIC2 with CLUSTER-B NIC2 by cat6 cable and CLUSTER-A NIC3 with CLUSTER-B NIC3 with other cat6 cable.
9- DELETE .. virtual (Mgmt) in CLUSTER-A THEN manage nodes from GATEWAY IN CLUSTER-B to create cluster network configurations and virtual SET switch in CLUSTER-A by powershell
Invoke-Command -ComputerName "CLUSTER-A" -ScriptBlock {New-VMSwitch -Name SETSwitch - EnableEmbeddedTeaming $TRUE -EnableIov $true -NetAdapterName NIC1,NIC2,NIC3
RESULT >>
NIC1 - (Mgmt)
NIC2 - (SMB01)
NIC3 - (SMB02)
10- be sure to complete all cluster configure and check new virtual SETSwitch to hold NIC1 as management network
11- now connect GATEWAY , Primary Domain to SETSwitch in CLUSTER-A.
12- do the same ABOVE steps in CLUSTER-B.
THE RESULT>>>
every things work good NO ERROR when i RUN powershell
Test-Cluster -Node "CLUSTER-A,CLUSTER-B" -Include "Storage Spaces Direct","Inventory","Network","System Configuration","Hyper-V Configuration"
### BUT ###
when i restart any node i can't connected from LAN even i ping to it.. until i take off both cable from NIC2 and NIC3 then the system work
i have tried to check from inside by access ANY GATEWAY server i see i can ping and every thing work !! before i take off both cable..
if i connect both nodes NIC2,NIC3 to physical switch and run test cluster i got error
the same cluster network, yet address is not reachable from 172.16.1.1 using UDP on port 3343.
MY QUESTION HERE >> is it important to be my domain outside nodes or must used other cables rather than cat6 for connect two nodes directly .. or any suggestions??
_________
Scenario#2
_________
1- create 4 nodes virtual environment by HYPER-V for CLUSTER-A, CLUSTER-B, DOMAIN and GATEWAY
2- create 3 virtual switch adapter (Mgmt),(SMB01),(SMB02)
2- connect all by virtual adapter (Mgmt)
3- add (SMB01),(SMB02) to CLUSTER-A and CLUSTER-B
4- make sure (SMB01),(SMB02) configure to include MAC address spoofing in adapter feature.
5- from GATEWAY server install cluster feature and network configuration in both CLUSTER-A, CLUSTER-B and test cluster.
RESULT>>>
Fine NO ERROR
BUT
when i disable MAC address spoofing in adapter feature and test cluster in both nodes
the same cluster network, yet address is not reachable from 172.16.1.1 using UDP on port 3343.
MY QUESTION
is possible to do enable MAC address spoofing in real physical adapter
or you have any ideas about that