[TD-LINUX] Network Bonding.docx

Linux network bonding guide

 

Configuring the environment

bond0

LAN1 port 1( device name : eno1) & LAN2 port 1 (device name: ens2f0)

 

bond1

LAN1 port 4( device name : eno4) & LAN2 port 4 (device name: ens2f3)

 

We will configure two network bonding, named respectively bond0, bond1.

If you configure one bonding , you only need to configure bond0.

 

1) Step1 : NetworkManger service stop and disable

[root@isvnap1p network-scripts]# systemctl stop NetworkManager

[root@isvnap1p network-scripts]# chkconfig NetworkManager off

Note: Forwarding request to 'systemctl disable NetworkManager.service'.

Removed symlink /etc/systemd/system/multi-user.target.wants/NetworkManager.service.

Removed symlink /etc/systemd/system/dbus-org.freedesktop.NetworkManager.service.

Removed symlink /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service.

 

2) Step2 : configure Network device bond0, bond1

[root@isvnap1p network-scripts]# cat /etc/modprobe.d/bond.conf

alias bond0 bonding

alias bond1 bonding

 

#### bond0 device

[root@isvnap2p network-scripts]# cat ifcfg-bond0

DEVICE=bond0

IPADDR=192.168.100.182

NETMASK=255.255.255.0

GATEWAY=192.168.100.1

USERCTL=no

BOOTPROTO=none

ONBOOT=yes

BONDING_OPTS="mode=1 miimon=100"

 

[root@isvnap2p network-scripts]# cat ifcfg-eno1

DEVICE=eno1

USERCTL=no

ONBOOT=yes

MASTER=bond0

SLAVE=yes

BOOTPROTO=none

 

[root@isvnap2p network-scripts]# cat ifcfg-ens2f0

DEVICE=ens2f0

USERCTL=no

ONBOOT=yes

MASTER=bond0

SLAVE=yes

BOOTPROTO=none

 

#### bond1 device

[root@isvnap2p network-scripts]# cat ifcfg-bond1

DEVICE=bond1

IPADDR=192.168.100.192

NETMASK=255.255.255.0

GATEWAY=192.168.100.1

USERCTL=no

BOOTPROTO=none

ONBOOT=yes

BONDING_OPTS="mode=1 miimon=100"

 

[root@isvnap2p network-scripts]# cat ifcfg-eno4

DEVICE=eno4

USERCTL=no

ONBOOT=yes

MASTER=bond1

SLAVE=yes

BOOTPROTO=none

 

[root@isvnap2p network-scripts]# cat ifcfg-ens2f3

DEVICE=ens2f3

USERCTL=no

ONBOOT=yes

MASTER=bond1

SLAVE=yes

BOOTPROTO=none

 

3) Step3 : configure Network device bond0, bond1

[root@isvnap2p network-scripts]# service network restart

 

4) Check  the bonding device IP is correctly assigned 

[root@isvnap1p ~]# ifconfig -a

bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500

        inet 192.168.100.181  netmask 255.255.255.0  broadcast 192.168.100.255

        inet6 fe80::f603:43ff:fe43:26f8  prefixlen 64  scopeid 0x20<link>

        ether f4:03:43:43:26:f8  txqueuelen 1000  (Ethernet)

        RX packets 10240  bytes 1664280 (1.5 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 531  bytes 77977 (76.1 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

bond1: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500

        inet 192.168.100.191  netmask 255.255.255.0  broadcast 192.168.100.255

        inet6 fe80::4adf:37ff:fe09:c713  prefixlen 64  scopeid 0x20<link>

        ether 48:df:37:09:c7:13  txqueuelen 1000  (Ethernet)

        RX packets 2468  bytes 215889 (210.8 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 46  bytes 7198 (7.0 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

eno1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500

        ether f4:03:43:43:26:f8  txqueuelen 1000  (Ethernet)

        RX packets 94  bytes 11885 (11.6 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 83  bytes 11464 (11.1 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 16