Difference between revisions of "Linux: Interface BONDING"
Onnowpurbo (talk | contribs) |
Onnowpurbo (talk | contribs) |
||
(9 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
Sumber: https://help.ubuntu.com/community/UbuntuBonding | Sumber: https://help.ubuntu.com/community/UbuntuBonding | ||
+ | |||
+ | '''WARNING''' | ||
+ | Jika di lakukan di Ubuntu 18.04 perlu di delete referensi ke interface jaringan (spt enp3s0) di | ||
+ | |||
+ | * /etc/netplan/ | ||
+ | * /etc/cloud/cloud.cfg.d | ||
==Install Pendukung== | ==Install Pendukung== | ||
− | apt install ifupdown | + | apt install ifupdown ifenslave |
− | |||
==Aktifkan Module== | ==Aktifkan Module== | ||
Line 16: | Line 21: | ||
# This file contains the names of kernel modules that should be loaded | # This file contains the names of kernel modules that should be loaded | ||
# at boot time, one per line. Lines beginning with "#" are ignored. | # at boot time, one per line. Lines beginning with "#" are ignored. | ||
− | + | ||
− | + | bonding mode=6 miimon=100 | |
− | |||
− | |||
− | bonding | ||
Aktifkan module | Aktifkan module | ||
Line 27: | Line 29: | ||
modprobe bonding | modprobe bonding | ||
modinfo bonding | more | modinfo bonding | more | ||
− | |||
==Edit Interface== | ==Edit Interface== | ||
sudo vi /etc/network/interfaces | sudo vi /etc/network/interfaces | ||
− | |||
− | |||
# enp3s0 is manually configured, and slave to the "bond0" bonded NIC | # enp3s0 is manually configured, and slave to the "bond0" bonded NIC | ||
Line 39: | Line 38: | ||
iface enp3s0 inet manual | iface enp3s0 inet manual | ||
bond-master bond0 | bond-master bond0 | ||
− | + | # bond-primary enp3s0 | |
− | # | + | # enp4s0 ditto, thus creating a 2-link bond. |
− | auto | + | auto enp4s0 |
− | iface | + | iface enp4s0 inet manual |
bond-master bond0 | bond-master bond0 | ||
Line 50: | Line 49: | ||
auto bond0 | auto bond0 | ||
iface bond0 inet static | iface bond0 inet static | ||
− | address 192.168. | + | address 192.168.0.9 |
− | gateway 192.168. | + | gateway 192.168.0.223 |
netmask 255.255.255.0 | netmask 255.255.255.0 | ||
− | + | # bond-mode active-backup | |
− | + | # bond-miimon 100 | |
− | bond-slaves | + | # bond-slaves none |
+ | bond-slaves enp3s0 enp4s0 | ||
+ | |||
+ | |||
+ | Edit | ||
+ | |||
+ | vi /etc/modprobe.d/bonding | ||
+ | |||
+ | alias bond0 bonding | ||
==Aktifasi Bonding== | ==Aktifasi Bonding== | ||
Line 61: | Line 68: | ||
sudo start networking | sudo start networking | ||
+ | atau | ||
+ | |||
+ | /etc/init.d/networking restart | ||
Atau | Atau |
Latest revision as of 07:51, 13 December 2019
Sumber: https://help.ubuntu.com/community/UbuntuBonding
WARNING Jika di lakukan di Ubuntu 18.04 perlu di delete referensi ke interface jaringan (spt enp3s0) di
- /etc/netplan/
- /etc/cloud/cloud.cfg.d
Install Pendukung
apt install ifupdown ifenslave
Aktifkan Module
sudo su vi /etc/modules
# /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. bonding mode=6 miimon=100
Aktifkan module
modprobe --first-time bonding modprobe bonding modinfo bonding | more
Edit Interface
sudo vi /etc/network/interfaces
# enp3s0 is manually configured, and slave to the "bond0" bonded NIC auto enp3s0 iface enp3s0 inet manual bond-master bond0 # bond-primary enp3s0 # enp4s0 ditto, thus creating a 2-link bond. auto enp4s0 iface enp4s0 inet manual bond-master bond0 # bond0 is the bonding NIC and can be used like any other normal NIC. # bond0 is configured using static network information. auto bond0 iface bond0 inet static address 192.168.0.9 gateway 192.168.0.223 netmask 255.255.255.0 # bond-mode active-backup # bond-miimon 100 # bond-slaves none bond-slaves enp3s0 enp4s0
Edit
vi /etc/modprobe.d/bonding
alias bond0 bonding
Aktifasi Bonding
sudo start networking
atau
/etc/init.d/networking restart
Atau
ifup bond0 ifdown bond0
Cek
cat /proc/net/bonding/bond0
ifconfig
Catatan
Mode 0
balance-rr
Round-robin policy: Transmit packets in sequential order from the first available slave through the last. This mode provides load balancing and fault tolerance.
Mode 1
active-backup
Active-backup policy: Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bond's MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. The primary option affects the behavior of this mode.
Mode 2
balance-xor
XOR policy: Transmit based on selectable hashing algorithm. The default policy is a simple source+destination MAC address algorithm. Alternate transmit policies may be selected via the xmit_hash_policy option, described below. This mode provides load balancing and fault tolerance.
Mode 3
broadcast
Broadcast policy: transmits everything on all slave interfaces. This mode provides fault tolerance.
Mode 4
802.3ad
IEEE 802.3ad Dynamic link aggregation. Creates aggregation groups that share the same speed and duplex settings. Utilizes all slaves in the active aggregator according to the 802.3ad specification.
Prerequisites:
- Ethtool support in the base drivers for retrieving the speed and duplex of each slave.
- A switch that supports IEEE 802.3ad Dynamic link aggregation. Most switches will require some type of configuration to enable 802.3ad mode.
Mode 5
balance-tlb
Adaptive transmit load balancing: channel bonding that does not require any special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed receiving slave.
Prerequisites:
- Ethtool support in the base drivers for retrieving the speed of each slave.
Mode 6
balance-alb
Adaptive load balancing: includes balance-tlb plus receive load balancing (rlb) for IPV4 traffic, and does not require any special switch support. The receive load balancing is achieved by ARP negotiation. The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware address of one of the slaves in the bond such that different peers use different hardware addresses for the server.