So for this, you don’t need to configure anything different on the switch.
#Nes app switch mac#
When that happens, the switch will learn that the MAC address for that server, has failed over to the bottom port. It’s only if the top port fails, it will failover to the bottom port. In our example here, all traffic is going out of that top port.
I give it that one IP address, 10.10.10.10, on that logical interface. I’ve got my physical server with the two physical network cards in there.
So looking at the Active/Standby redundancy, you can see the same example again here. Traffic is always going out only one interface at a time. The disadvantage of using Active/Standby, the good thing is it gives you the redundancy, but you don’t get any load balancing. It’s still connecting the one IP address. So any client that is connecting to that host doesn’t need to change anything. If it fails or if the actual cable it’s connected with fails, or if the switch port on the other side fails, then we’ll automatically fail over to the other physical port, still using the same IP address. If that port fails, the traffic will automatically fail over to the other port, and for Active/Standby redundancy, you don’t need to configure anything on the attached switch.Īctive/Standby gives us redundancy. With Active/Standby, all traffic will go out one physical port. Our first option is we can do Active/Standby for the NIC teaming. I said earlier that the reason we do the NIC teaming is so that we can get redundancy, and optionally, load balancing. So, all of those terms basically mean the same thing. If we’re talking about bundling multiple physical ports on a switch into a single logical interface, we’ll call that either a port channel, etherchannel, or a link bundle. So those are names when we’re talking about it on a server.
Those are just different terms that all mean the same thing. It can also be known as bonding, balancing, or link aggregation. It’s much easier if you can just use that one IP address on both those network cards, so you need to do NIC teaming to be able to do that.ĭepending on the documentation that you’re reading, there are many different names for NIC teaming. It also makes it difficult to figure out how the redundancy and the failover are going to work for your host connecting in. Then you’ve got the same host being reached through two different IP addresses, and this makes your networking much more complicated. This allows me to have a single IP address, which is 10.10.10.10 in our example here, being used across two different physical interfaces.Īnother thing you could do is use two different IP addresses on your two different NICs. You can see in the diagram here, I’ve got my physical server, which has got two different physical network cards in there, and I grouped those into a single logical interface. This can be used to give you the benefits of load balancing and redundancy across multiple physical interfaces. NIC teaming allows you to combine your physical NICs, which are your Network Interface Cards, into a single logical interface.
0 kommentar(er)
