- HOW TO CONFIGURE NIC BONDING IN REDHAT LINUX 7 HOW TO
- HOW TO CONFIGURE NIC BONDING IN REDHAT LINUX 7 MAC
How To Configure Network Bonding or NIC Bonding Using Network Scripts In RHEL 7 & RHEL 8ġ. To view all the bonds on the system, either up or down, use the command, # cat /sys/class/net/bonding_masters
The sysfs filesystem, as we already learnt, is a virtual file system that presents the current situation of whatsoever that is happening in the kernel in form of files and directories, and these objects (files and directories) can be manipulated just as you would manipulate any other type of filesystems with the different Linux utilities. When you finally get the mode that will be suitable for your system, you can then edit the bond configuration file, and add the bonding mode to it. The good thing about bonding is that if you are not really sure of the bond mode that will be suitable for your system or network environment, you can edit the bonding information in the sysfs filesystem in the location, /sys/class/net without having to edit the bond configuration file, just restart the interface, and the new configuration happens immediately. Suggested: Managing The Linux Kernel Module
A numeric way of specifying this mode is using the number, (2) This mode can also be specified as balance-xor.
HOW TO CONFIGURE NIC BONDING IN REDHAT LINUX 7 MAC
Here, the calculation is done in a way that the MAC address of the slave NIC is measured with the Mac address of the incoming packets, once there is a confirmed connection, the same NIC will be used for the destination MAC address. random: Packets will be transmitted on selected ports randomly. A numeric way of specifying the broadcast runner is using the number, (3)į). broadcast: Packets will be broadcast/transmitted over all the interfaces/ports. You can Click here to know more about tlb and albĮ). (ii) Adaptive load balancing (alb): A numeric way of specifying alb is using the number, (6). (i) Adaptive transmit load balancing (tlb): A numeric way of specifying tlb is using the number, (5) loadbalance: The transmitted packets will be load balanced/distributed across all the interfaces/ports with active Tx load balancing and Berkeley Packet Filter (BPF)-based Tx port selectors. To use this runner on the system, lacp(802.3ad) must also be configured on the network switch, hence the switch must support IEEE 802.3ad dynamic link.ĭ). This runner can also be specified as 802.3ad.Ī numeric way of specifying the lacp runner is using the number, (4). It supports both fault tolerance, and load balancing. It uses the the 802.3ad protocol for link aggregation. lacp: Known as dynamic link aggregation makes all the aggregated links/interfaces act as one for higher throughput. A numeric way of specifying the roundrobin runner is using the number, (0).Ĭ). This runner/mode can also be specified as (balance-rr). This runner/mode will do or rather supports both load balancing and fault tolerance. roundrobin: Packets will be transmitted over all the interfaces/ports in turn, i.e, turn by turn. A numeric way of specifying activebackup runner/mode is using the number, (1).ī). activebackup: One interface/port will be active while the other interfaces/ports will be a backup for the active one in case it fails. Let’s understand how these modes or runners work.Ī). There are different types of modes / runners which are active-backup, round-robin, lacp, load balancing, broadcast, and random. So, in summary, it is safe to say that network teaming is a new way of implementing network aggregation for a bigger throughput & redundancy, and an alternative to network bonding. Teaming also came with some feature differences from bonding, hence, teaming is an alternative to bonding and not a replacement of bonding.ĭepending on the requirements and the features you need, one can either implement or configure network bonding or network teaming.Ĭlick here to see the differences between network bonding and network teaming features Prior to Red Hat Enterprise Linux 7 (RHEL 7), the implementation of this concept of network aggregation for a bigger throughput and redundancy is called bonding.Īs RHEL 7 came by, the implementation of this concept was changed from bonding to teaming, however, teaming came with its own driver, entirely different from bonding’s driver. What Is The Difference Between Teaming and Bonding In Linux This concept in Linux is commonly called bonding. The combination of two or more network links to provide a bigger network throughput or redundancy is known by many names such as (channel bonding, Ethernet bonding, channel teaming, NIC teaming, port trunking, port channel, link aggregation, etc). NIC teaming and NIC bonding are often used interchangeably, however, they are different. What is Network Teaming and Network Bonding (NIC Teaming & NIC Bonding)