Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 10672

Scale Out File Server & Networking

$
0
0

Hi

I am in the process of creating a SOFS and all is going swimmingly but am getting confused on the networking side of things.

I have my CSVs & SMB Cluster running fine on two servers and have provisioned a file share OK.  Now I want to make a VM on the SOFS but I want all the storage action to run over my 10G switches and not the public network.  This is where I am getting confused.

On the two SOFS I have the following networks in Cluster Manager:

1. "Public Network" - 192.168.30.0/32 - this is where all my existing VMs live and people access resources from

2. "Cluster Network" - 4 X NIC in each SOFS connected via crossover cable for Cluster Traffic.  NICs are Teamed, subnet is 10.10.1.0

3. "SMB Network" - 2 X 10G NIC in each SOFS & HV Server connected to 2 X 10G switches.  NICs Teamed, subnet as per Cluster Network.  I would like any SMB traffic to go over these NICs

So in Failover Cluster Manager I have the 30.0 network configured for Client Access.  It has registered the SOFS in DNS OK, I can reach the SOFS from anywhere in the 30.0 network

The Cluster & SMB networks are not configured for Client Access but for Cluster Traffic.  Even though I have set a subnet of 10.10.1.0 on my 10G NICs under Networks in Cluster Manager it says the 10G network is using the 10.0.0.0 subnet.

Does this mean I have to change my NIC Team adapter properties to reflect this subnet?  Where did it get this subnet from?

I have attempted to create a new VM in Hyper-V on the SOFS File Share but it uses the 30.0 network and not the 10G Team I have created to access the SOFS share.

Where I am going wrong?

Thanks!


Viewing all articles
Browse latest Browse all 10672

Trending Articles



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