![]() ![]() This mode provides load balancing and fault tolerance.īroadcast policy: transmits everything on all slave interfaces. Alternate transmit policies may be selected via the xmit_hash_policy option, described below. XOR policy: Transmit based on the selected transmit hash policy. The bond’s MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. A different slave becomes active if, and only if, the active slave fails. This mode provides load balancing and fault tolerance.Īctive-backup policy: Only one slave in the bond is active. Round-robin policy: Transmit packets in sequential order from the first available slave through the last. Below is an excerpt from that documentation that describes each bond mode: ![]() Depending on the bonding mode you choose, you could have an active/passive scenario where one port activates only if the other appears off-line, or you could have an active/active scenario where you accept traffic across all ports.įull documentation of all of the Ethernet bonding modes is available in the Documentation/networking/bonding.txt file included with any Linux kernel source. With Ethernet bonding you can have multiple Ethernet ports that answer to the same IP address. Most servers these days come with at least two Ethernet ports if not more, so it makes sense to set up Ethernet bonding, especially when you see how easy it is.Įthernet bonding is a feature built into the Linux kernel as a module. If you want to be able to survive switch failure or maintenance, you need a system with multiple Ethernet ports connected to redundant switches. After all, switches need maintenance from time to time and they do fail, as do networking cards and even Ethernet cables. ![]() As you develop fault-tolerant systems, you quickly realize that after disk failures, network issues are probably the second area that requires redundancy. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |