Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

Scale out file server hyper-v DNS best practices with SMB multichannel

$
0
0

TL;DR I cannot get hyper-v hosts to "see" cluster servers through DNS and thus cannot add shares to CSV (at least through Server Manager).

I am in the middle of setting up a scale out file server for hyper-v. Setup is thus:

(to get a basic idea of how it looks see this article)

All servers running Windows Server 2012.

Subnet 1 (SAN): 192.168.1.0/24 includes cluster servers and iSCSI target server
Subnet 2 (heartbeat) 192.168.2.0/24 includes cluster servers directly linked to eachother
Subnet 3 (hyper-v 1) 192.168.3.0/24 includes cluster servers and hyper-v hosts*
Subnet 4 (hyper-v 2) 192.168.4.0/24 includes cluster servers and hyper-v hosts*
Subnet 5 (control/infrastructure) 192.168.5.0/24 includes every server for control/access i.e. Server Manager, Remote Desktop, DC, DNS

* For SMB multichannel (see linked article above)

Each server has the appropriate amount of NICs depending on their subnet membership as listed above.

My initial attempt got as far as bringing the cluster up but then could not add SMB shares on the CSV. Everything showed the cluster as up and operating and I could even browse to C:\ClusterStorage\Volume1 and create folders. But I could not add a share. When I opened the 'Add a Share' window in Server Manager all options would be grayed out but no error would pop up. It just wouldn't allow me to see the cluster share and add a shared directory.

Every node is pingable within their own subnet and I can access every node through the control network with server manager or remote desktop. I have turned off firewall on everything just to minimize issues and get everything running.

I read somewhere that it's likely a DNS issue and that brings me to my main question:

What is best practice? I already have a DC/DNS server on the control network and I know you are not supposed to multihome a DC/DNS server so what do I do? Add secondary DNS servers to Subnets 3/4 so they can resolve eachother? Add an RRAS server to route between subnets so they can all access the DC/DNS server that already exists? Manually modify local host files for hyper-v hosts to resolve cluster servers on Subnets 3/4?

Help!


Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>