Ubuntu quick Nic bonding configuration

The quick configuration of bonding Nic In ubuntu can improve network processing capability and network interface redundancy. prerequisites: there are at least two available NICs. The following describes how to quickly configure bonding in simple steps: 1. after the kernel module vi/etc/modules is loaded and bonding is configured, it is similar to the following: #/etc/modules: kernel modules to load at boot time. # This file contains the names of kernel modules that shoshould be loaded # at boot time, one per line. lines beginning with "#" are ignored. looplprtcbonding2. disconnect the network stop networking3. load the module modprobe bonding4. edit the NIC configuration and add bondingv I/etc/network/interfaces eth0 eth1 is set to bonding mode. After editing, it is similar to the following: # This file describes the network interfaces available on your system # and how to activate them. for more information, see interfaces (5 ). # The loopback network interfaceauto loiface lo inet loopback # The primary network interfaceauto eth0iface eth0 inet manualbond-master bond0auto eth1iface eth1 inet manualbond-master bond0auto bond0ifbo Nd0 inet static address 192.168.1.110 netmask 255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 # load balancing and fault tolerance # bond-mode balance-rr bond-mode 802.3ad bond-miimon 100 bond-lacp-rate 1 bond-slaves none # bond-downdelay 200 # bond-updelay 200 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.15. start Network Networking Note: Here there are multiple bond-mode options, which can be set according to the actual situation and needs: Mode 0balance-rrRound-robin policy: transmits packets sequentially starting from the first available slave Nic. server Load balancer and fault tolerance capabilities. Mode 1active-backupActive-backup policy: At the same time, only one network adapter is in working Mode, and the other is enabled only when active fails. mode 2balance-xorXOR policy: transmits data packets based on the target mac exclusive or operation, and provides load balancing and fault tolerance capabilities. mode 3 broadcastBroadcast policy: All data packets must be transmitted to all slave instances, which is highly fault tolerant. mode 4802.3ad complies with IEEE 802.3ad specifications. mode 5balance-tlb Adaptive Load Balancing: the outbound traffic is based on the current slave rate. incoming traffic is received by the current active slave. if the inbound processing fails, other slave will take over. mode 6balance-alb Adaptive Load Balancing: Includes tlb and rlb, inbound load is Based on arp negotiation.