Is it possible to use only 2 subnets including iSCSI to run Windows 2016 cluster?

Hi, We're about to create a Windows 2016 cluster.  It's a small cluster with 2 members.  We usually use multiple subnets: live migration, cluster, management, iSCSI

But Live migration will not be used very often.  Each server has 4x 10G Intel NIC   Of course 2 NIC will be used pour iSCSI so I'll keep the iSCSI network for the cluster.  But I'd prefer to keep only one subnet (one vlan) for everything else.

All ports are connected to 2x Force10 switch.  NIC teaming will be used.  LACP is already configured in access mode on both switch (the Force10 are configured in VLT or Virtuel Link Trunk)  The iSCSI network has its own VLAN as well as the LAN.

I want to keep things simple.  

I guess this is not the recommended setup.  But i'd like to have your advice.  

Thanks
kt3zAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dan McFaddenSystems EngineerCommented:
You are building a Hyper-Converged Failover Cluster...

General knowledge with FoC.. you need 2 dedicated networks:

1.  Client Access (needs AD connected networking)
2.  Cluster communications (can be a direct cross over, IPv4 (IP/SNM only, no gateway, no DNS, no NetBIOS, no client protocols) or IPv6 configured)

If you do not have 2 separate networks, the cluster validation test will finish with warnings that the cluster does not meet the recommended best practices.  So the answer is, you could build the cluster with on 1 network, but it is not a recommended best practice.

Also, Microsoft teaming, when created thru the Server Manager, does not support RDMA therefore you will lose some functionality that may affect performance.

Reference link:  https://technet.microsoft.com/en-us/library/mt403349.aspx#bkmk_sswitchembedded

I am building a similar setup, 2 node hyper-converged Failover Cluster with Storage Spaces Direct (no shared storage) on Server 2016.

I have 4 networks.

1.  Client Access (can see AD & the rest of the infrastructure) [teamed 10G ports, IPv4 fully configured, IPv6 enabled local-link only]
2.  Cluster Comm [direct 1G cross-over, IPv4 address and subnetmask only]
3.  Storage 01 [10G port, connected to a VMSwitch with RDMA enabled for teaming, IPv6 local-link no IPv4]
4.  Storage 02 [10G port, connected to a VMSwitch with RDMA enabled for teaming, IPv6 local-link no IPv4]

The storage network will support live migration and the storage bus (SMB BUS for storage spaces direct)

Reference links:
1. Microsoft S2D: https://technet.microsoft.com/en-us/windows-server-docs/storage/storage-spaces/hyper-converged-solution-using-storage-spaces-direct#step-1-deploy-windows-server
2. 2 Node example: https://www.tech-coffee.net/2-node-hyperconverged-cluster-with-windows-server-2016/

Dan
0
kt3zAuthor Commented:
Sorry I should have told you but hyperconverging is not an option for us.  it's less expensive to have a Compellent SC4020 (10 SSD 1.9TB + 14 SATA 1.8TB) in tiering.  Windows 2016 is way too expensive.  Besides it takes at least 3 but more likely 4 servers to hyperconverge and Windows 2016 datacenter is required and it's per core pricing.  We only need 2 servers.   It's less expensive to buy a SC4020 with 2 servers.  

I use 2 networks: the cluster network is the LAN and iSCSI.  That's it.  With 20G we don't really need to create a VLAN for the cluster, another for live migration and another and another.  

I think S2D will gain in popularity someday when or if the pricing will go down.  But it's too expensive and too early for us.  

Thanks again
0
Dan McFaddenSystems EngineerCommented:
Just so I understand your setup, you are building a cluster to support Hyper-V VMs, correct?

I would not recommend just a single subnet.  In the event that a Live Migration does happen, it would be possible that the migration would significantly disrupt client access during the event.  Separating your client access from your cluster communications from your Hyper-V Live Migration traffic is recommended.

You could combine the client access and cluster communications subnet (though Valid Cluster will complain), but I would keep Live Migration traffic isolated.

BTW:  since RTM, Server 2016 can do a Hyperconverged S2D cluster with only 2 nodes.  I am currently testing the configuration for production deployment.

Dan
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Clustering

From novice to tech pro — start learning today.