[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

Server 2012 NIC Teaming - SMB Traffic on specific VLAN/NIC Teaming

Posted on 2014-12-19
1
Medium Priority
?
306 Views
Last Modified: 2015-01-06
Hi Guys,

I've got a Scale Out File Server setup in a 2 node cluster with JBOD storage. I've also got two Hyper-V servers which will be utilizing this as it's storage over SMB 3.0

I want to use converged fabrics in the Hyper-V hosts. There's 8 1GB NICS in the Hyper-V hosts and 4 1GB NICS in the SOFS.

On the Hyper-V hosts I want to make a NIC team of 6Gbps and put storage, heartbeat, management and live migration all down that pipe. I'll have another NIC team of x2 1Gbps connections for VM traffic.

How do I ensure certain traffic in the 6Gbps NIC team goes on the correct VLAN? At the minute it's just going to go over the management VLAN. I've got VLANS for Storage, LM and Cluster Heartbeat and the NICS can see them all because the ports they're plugged into on the switch are all trunk ports.

Anyone know how I would achieve this?

Cheers guys!

Jack
0
Comment
Question by:Jack Lloyd
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 39

Accepted Solution

by:
Philip Elder earned 2000 total points
ID: 40510359
Our starting point for this setup is:
+ SoFS Node: (2) x540T2 10GbE
+ Hyper-V Node: (2) x540T2 10GbE
+ (2) NETGEAR XS712T 10GbE Switches

Port 0 on each x540T2 gets plugged into XS712T-1. Port 1 on each x540T2 gets plugged into XS712T-2.

This gives us dual redundant paths for our I/O.

From there we have four subnets: 192.168.110.0/24, 192.168.120.0/24, 192.168.130.0/24, 192.168.140.0/24.

Each 10GbE port would be set up as follows:
SoFS Node 1: 192.168.110.10, .120.10 , .130.10, .140.10
SoFS Node 2: 192.168.110.20, .120.20 , .130.20, .140.20
Hyper-V Node 1: 192.168.110.30, .120.30 , .130.30, .140.30
Hyper-V Node 2: 192.168.110.40, .120.40 , .130.40, .140.40

This gives us SMB Multi-Channel between compute and storage in the form of four 10GbE pathways.

I would _NOT_ run 1GbE for storage I/O. This is asking for trouble. SoFS setups and iSCSI are definitely not similar in their architecture.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Creating an OSPF network that automatically (dynamically) reroutes network traffic over other connections to prevent network downtime.
Previously, on our Nano Server Deployment series, we've created a new nano server image and deployed it on a physical server in part 2. Now we will go through configuration.
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
How to fix incompatible JVM issue while installing Eclipse While installing Eclipse in windows, got one error like above and unable to proceed with the installation. This video describes how to successfully install Eclipse. How to solve incompa…
Suggested Courses

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question