The following are different types of etherchannel bonding modes: If one of the underlying physical adapters goes down, then the other physical adapter is used to handle the communication traffic. The IP address will be configured on this virtual interface. Please see the command as below.In Linux, using etherchannel bonding you can combine two or more physical network interfaces (NIC) together to create a virtual interface. Note: Manually down and up the Slave Interfaces to check the working of Channel Bonding. Thu Sep 12 14:40:37 2013Įthernet Channel Bonding Driver: v3.6.0 (September 2īonding Mode: fault-tolerance (active-backup) 1 cat /proc/net/bonding/bond0 Sample Outputīonding Mode is showing fault-tolerance (active-backup) and Slave Interface is up. # service network restart Shutting down interface bond0: Ĭhecking the status of the bond with command. Restart network service and check the status of bonding. # vi /etc/sysconfig/network-scripts/ifcfg-bond0 DEVICE=bond0 only one change will be there in the bond interface ifcfg-bond0 instead of ‘ 0‘ it will be ‘ 1‘ which is shown as under. In this scenario, Slave interfaces remain same. Every 0.1s: cat /proc/net/bonding/bond0 Thu Sep 12 14:08:47 2013Įthernet Channel Bonding Driver: v3.6.0 (September 26, 2009)īonding Mode: load balancing (round-robin) 1 cat /proc/net/bonding/bond0 Sample Ouputīelow output shows that Bonding Mode is Load Balancing ( RR) and eth1 & eth2 are showing up. # service network restart Shutting down interface bond0: Ĭhecking the status of the bond. Restart Network service and interfaces should be OK. TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:7989 errors:0 dropped:0 overruns:0 carrier:0 RX packets:385 errors:0 dropped:0 overruns:0 frame:0 TX packets:8072 errors:0 dropped:0 overruns:0 carrier:0 RX packets:16989 errors:0 dropped:0 overruns:0 frame:0 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 TX packets:16060 errors:0 dropped:0 overruns:0 carrier:0 RX packets:17374 errors:0 dropped:0 overruns:0 frame:0 UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 # ifconfig bond0 Link encap:Ethernet HWaddr 00:0C:29:57:61:8E Let’s see interfaces created using ifconfig command which shows “ bond0” running as the MASTER both interfaces “ eth1” and “ eth2” running as SLAVES. Note: In the above configuration we have chosen Bonding Options mode=0 i.e Round-Robin and miimon=100 ( Polling intervals 100 ms). The following is a sample channel bonding configuration file. # vi /etc/sysconfig/network-scripts/ifcfg-eth2 DEVICE="eth2"Ĭreate bond0 and configure Channel bonding interface in the “ /etc/sysconfig/network-scripts/” directory called ifcfg-bond0. Here also, specify parameter MASTER bond0 and eth2 interface as a SLAVE. # vi /etc/sysconfig/network-scripts/ifcfg-eth1 DEVICE="eth1" Mention parameter MASTER bond0 and eth1 interface as a SLAVE in config file as shown below. Load Balancing (Round-Robin) Configure eth1 Need superuser privileged to execute below commands. We have two Network Ethernet Cards i.e eth1 and eth2 where bond0 will be created for bonding purpose. Other Interface Card will be active only if the active slave NIC fails.
#How to configure nic bonding in redhat linux 7 driver#
Channel/ NIC bonding will work with the help of bonding driver in Kernel. If one physical NIC is down or unplugged, it will automatically move resources to other NIC card. This is a great way to achieve redundant links, fault tolerance or load balancing networks in production system. Ethernet Channel Bonding enables two or more Network Interfaces Card ( NIC) to a single virtual NIC card which may increase the bandwidth and provides redundancy of NIC Cards.