Configuring and Understanding NIC Teaming in Server 2016

this is a sample from our training at itv.com if you'd like to learn more please go to IT DVDs comm now let's go over to server manager and for nic teaming here let's click on disabled so we're gonna create a team out of these two NICs which makes it look like one Nick that's going to give us some load balancing so we can use both NICs at the same time and it's going to give us some redundancy so that if one NIC goes down the other NIC is still up and running and we're going to use two Nick's in this example but we could use more if we needed more bandwidth so we could use four or six even NICs if we needed to if we need more bandwidth than that we could use more gigabit NICs but we probably want to look at using a 10 gig Ethernet card with a 10 gig switch if it's possible so let's create our team here I'm gonna go to tasks new team and there's our two Nick's that we want to use in our team there's some additional properties down here that we're gonna be talking about if I scroll down a bit there's a teaming mode load balancing mode and standby adapter again we'll be talking about those in a bit and for the primary team interface if I click on this we can give it a name if we'd like by default it's automatically generated I'm gonna call this team interface though team one now down here we can specify if it should be put in a specific VLAN and we would do this if the ports on the switch these Knicks were connected to or configured as a trunk mine are not in this case they're configured to be any specific VLAN so I'll go ahead and click OK and click OK next we just need to give it a team name here and I'll call it team one ok and it may take a second for our NICs to come up but my team is created and now if we go look at our network connections here we can see there's this new NIC called team one and that's the one we would configure if we wanted to so but we're going to do that in a little bit that's the one we'd put an IP address on etc and you can see if we right-click on one of the team members go to properties all these boxes are now unchecked because this Nick is just part of the team we don't really configure these to Nick's anymore we configure this new Nick that was created now let's go back and look at some of the different options we had with our team here I'm gonna right-click on it and go to properties let's go to additional properties so we've got a teaming mode here we've got static teaming switch independent and LACP so with switch independent it doesn't matter which Nick is plugged into which switch so if we have multiple switches that are connected to each other we can connect one Nick to one switch and one Technic to another switch and it'll work just fine and that it's a very easy setup and that actually can give us some switch redundancy kind of like this here where we you know we have one Nick plug into one switch one Nick plugged in the other switch those switches are connected so traffic can flow all around but if this switch goes down well this Nick still connected to the good switch so we still have network connectivity with static teaming in LACP we're gonna need some configuration on the switch side and with a Cisco switch we would configure something called ether Channel so that the switch knows hey these two ports that the Knicks are plugged into on the switch these two ports are part of a team and with LACP we configure ports on our switch with the LACP protocol and then they can dynamically detect that they're part of the same team so we might be thinking man you know static teaming LACP there's more configuration it's much more difficult why would I want to use those instead of switch independent well with switch independent we get load balancing on traffic flowing out from our server to other destinations but traffic going back in to the server that type of load balancing would be handled by the switches it's connected to or the switches connected to in which case we would need some configuration on the switch like ether Channel so that we can get that load balance balancing for traffic going back into our hyper-v hosts so that's the advantage and we'll take a look at how to configure something like ether channel a little bit later on now let's take a look at the load balancing mode we've got and res hash and hyper-v port here these are the two older load balancing modes for address hash it decides which Nick to send the traffic out of in the team based upon a few factors like MAC address IP address for the destination where the traffic's trying to get to so what that means if I'm trying to talk to PHX DC 0 1 the traffic might go out this Nick because it's talking to a specific MAC address IP address if there's another server over here the hash is going to be different because it's a different MAC address is trying to go to and a different IP address so it might send the traffic out on this Nick so that's how we get the load balancing for a hyper-v port it's going to use the port on the virtual switch wherever the traffic's coming out of to determine which physical Nick to use for traffic so if one virtual machine is trying to talk to one server and another virtual machine is trying to talk to another server then those traffic's might go out a different Nick's because they're on different ports and the virtual switch and then there's dynamic this is really the best of both worlds and probably what we're going to use most of the time and with this one outbound loads are distributed based on a hash of the TCP ports and IP addresses but the big advantage is in dynamic mode it also rebalances loads in real time so that a given outbound flow may move back and forth between team members and each one of these Nick as a team member so we really get some dynamic load-balancing and for a standby adapter if we want we can choose an adapter that isn't being used it's just waiting for a failure and then it jumps in and takes over if there's a failure really normally you're just going to want all the team members in there because we get that fail failover anyways so no real sense in having one Nick just sitting there doing nothing when it could be in use one thing I do want to note is that if we do use like a static teaming then the Nick's in the team are gonna have to be plugged into the same switch with ether channel in particular that's what Cisco uses for the switch side configuration so it looked more like this where we're plugged into one switch as opposed to getting some switch redundancy here by plugging into multiple switches but with Cisco switches and other switches they can be stackable so we can have actually multiple switches instead of being connected with ethernet cables or fiber cables there's actually something on the back of the switch that we connect it's normally proprietary type cable connection we connect from one switch to another switch and that makes it actually one big logical switch but if there's a failure then the other switch and the stack still works we're gonna have multiple switches in a stack you know four or five switches if we need to it actually makes it easy to administer as well as give us some redundancy so that's the way if we were going to use ether Channel how we'd get switch redundancies we'd use stackable switches

Channel: ITdvds

Views: 51,192

Rating: 4.8222222 out of 5

Keywords: Server 2016 Training, Server 2016 Teaming, NIC Redundancy

Id: _3MfjRqVIeo

Length: 7min 45sec (465 seconds)

Published: Thu Jan 18 2018