7

I have two questions which I will separate to avoid confusion.

I intend to build a network based on redundancy. There will be two pieces of every device, sometimes more than 2 such as NIC cards. I drew up this picture for you.

Network Diagram

As you can see I have two switches,one router and two servers. Each server will run Windows 2012 R2 Teaming,(Teams of 2),Each Team will be on its own VLAN (Please note this may change as the question 2 talks about it).

  1. My first question is, what type of logic does the NICs have for load balancing? , Do I have to Stack the switches together for it to work? , Can I just connect two ports of the router to each of the switches and NOT stack them (the switches)? , Will this then send traffic from switch A to router to switch B? ,I would prefer them to be completely independent, so if a switch fails or a NIC fails won't be a problem.

  2. My second question is about VLAN'ing. We have multiple independent processes running on the network (about 8). Where we would prefer that server A doesn't talk to server B if its not needed. This is making me create 8 different VLANs, and have each machine or VM have an IP address specifically on the VLAN. One or two computers need all 8. (There is a lot more than 2 servers, but for the picture sake, I only drew two for the example).

Is there a better way to do this? We are going to have the team VPN into the network, and I want them to be able to get to every switch/pc/vm, so I guess I would need another Administrator VLAN, adding another IP and another VNIC to each machine. There has to be a better way to do this.

Thank you all,

5
  • NICs don't really do load balancing, that is handled by the OS. I don't understand the whole VLAN thing. Server A would never talk to Server B unless it needs to, regardless of which VLAN it is on. You may want to take this question over to Server Fault since this seems more about servers than the network. – Ron Maupin Oct 21 '15 at 14:52
  • It's not clear what you mean by "prefer that A not talk to B." Do you want to isolate the servers so they can't talk to each other? Or keep VMs from talking to each other? – Ron Trunk Oct 21 '15 at 17:37
  • I would like to stop the servers from talking. For instance Server A gets a virus, I dont want B to be able to get it from A. (Not really often occurs, but just to explain the idea). There is just no reason for them to see each other, but as I was drawing out my design, I would have to make like 8 VLANs, with like 10 IPs per VLAN, is way getting out of control. I just imagine there has to be a better way to go about it. – KenBeanNet Oct 21 '15 at 18:29
  • If you route between the VLANs, the virus can still spread. VLANs just prevent the servers from talking at layer-2, but the router allows them to talk at layer-3. If one server can log into another server, the virus can spread, VLANs or not. You are trying to drive a nail with a screwdriver. VLANs have legitimate uses, but you seem to be going to a lot of trouble for no reason. Separate user accounts and anti-virus software are the proper tools for stopping the virus spread you describe. – Ron Maupin Oct 21 '15 at 22:47
  • Did any answer help you? if so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you could post and accept your own answer. – Ron Maupin Jan 4 at 1:42
2

it seams like we talk about some thing like that

enter image description here

My first question is, what type of logic does the NICs have for load balancing?

Logic design of load balancing is like the diagram ,each VM should has at lest two VNIC's (you may map each VNIC to physical NIC on th e server) which will be teamed as per your design and each VNIC will connected to different switch ,and port aggregation on the level of switches should be configured (which is call etherchanel or port-group).the etherchanel created on switches is connecting individual VM and assigned to VLAN as well.for example you could configure teaming between VNICs to use LACP as port aggregation and use mac-address hashing for example as a load balance mechanism and from the switch side you can configure ports connected to this VNICs as port-group and configure it as a LACP port aggregation and assign this port-group a VLAN.

Do I have to Stack the switches together for it to work?

Yes sure stack cause the two switches came as one switch which will allow you to configure etherchanel on the two switches.

Can I just connect two ports of the router to each of the switch and NOT stack the switches?

NO connecting the two switches to the router wont solve this issue you must stack both of them like the next diagram

enter image description here

Will this then send traffic from Switch A to Router to Switch B?

In this case you have full redundancy on the level of servers and the level of switches so there is no fear from any switch to came down or any NIC came down the only thing you may fear of that the server it self came down.

Is there a better way to do this?

The best way to accomplish this task is to configure the 8 vlan as a layer 2 on your switches and as layer 3 on the router and apply access list configuration on the router which will control the access of each host from vlan to another

1

You have two options when you cable a server like that, with one patch going to swtich A and another to B. Either have the server use one link at the time, aka. fail-over, or stack the switches and do LACP. LACP requires that all member ports are connected the same switch, but with stacking you can get around this.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.