# Linux Bonding Network

#### RedHat 7/8 with nmtui

nmtui > Edit a connection > Add > New Connection > Select Bond > Create

- Profile Name: bond0
- Device: bond0

> Slaves > Add

- Profile Name: eno1-slave NOTE: 建議這裡要加上 -slave，與實際的裝置名稱做區別
- Device: eno1
- Profile Name: ens3f0-slave
- Device: ens3f3

> IPv4 Configuration

- Address: 10.4.1.71/24
- Gateway: 10.4.1.254
- DNS Servers: 10.3.3.3

> IPv6 Configuration > Disabled

> Profile Name 的名稱會與實際設定檔名 ifcfg-XXX 有關，上述的設定會產生設定檔 ifcfg-bond0 , ifcfg-eno1-slave
> 
> 如果 Profile Name 設定錯了要修改，必須移除整個 Bond 設定，然後再重建；如果直接修改設定，關聯的設定檔名稱 ifcfg-XXX 並不會一起被更新，這會造成爾後管理上的困擾。

變更 Bonding 模式  
預設模式是使用 Load Balancing (Round-Robin)，將它變更為 Acitve-Backup

nmtui > Edit a connection > Bond: bond0 > Edit >

- Mode: Active Backup
- Primary: eno1 註:需要指定其中一張網卡為主要

> NOTE: 如果要使用預設的 Round-Robin 模式，網卡所連結的 Switch 設備必須設定 EtherChannel，否則 Switch 設備會偵測到 vlan XX is flapping between port YYY and port ZZZ。

重啟網路服務

```shell
# 注意:如果有使用 iSCSI Disks,重啟網路服務可能造成系統其他問題
systemctl restart network.service
or
nmcli networking off; modprobe -r bonding ; nmcli networking on
```

#### RedHat 8 with nmcli

網路環境: 三張網路裝置做 bonding

- ens3
- ens4
- ens5

```shell
# 檢視目前網路裝置
nmcli device status

# 新增 team 網路裝置
# 自訂名稱: team0 
nmcli connection add type team con-name team0 ifname team0 ipv4.addresses 192.168.10.20/24 ipv4.gateway 192.168.10.1 ipv4.dns 192.168.10.1 ipv4.method manual  connectio.autoconnect yes config '{"runner" : {"name" : "activebackup"}}'

# 檢查 team 0 狀態
nmcli device status

# 新增 team-slave 網路設備(綁定第一張網卡)
# 自訂名稱: team0-eth0
# master 指定剛剛新增的 team0
nmcli connection add type team-slave con-name team0-eth0 ifname ens3 master team0

# 新增 team-slave 網路設備(綁定第二張網卡)
# 自訂名稱: team0-eth1
# master 指定剛剛新增的 team0
nmcli connection add type team-slave con-name team0-eth1 ifname ens4 master team0

# 新增 team-slave 網路設備(綁定第三張網卡)
# 自訂名稱: team0-eth2
# master 指定剛剛新增的 team0
nmcli connection add type team-slave con-name team0-eth2 ifname ens5 master team0

# 檢查 team 0 狀態
nmcli device status
```

測試網路備援

```shell
# 檢視 team0 狀態
teamdctl team0 state
teamnl team0 options

# 關閉第三張網卡
nmcli connection down team0-eth2

# 檢查狀態
nmcli device status
teamdctl team0 state

# 開啟第三張網卡
nmcli connection up team0-eth2
```

#### LACP Mode

##### RedHat 7/8

nmtui > Edit a connection > Bond: bond0 > Edit >

- Mode: 802.3ad

Verify the state of the network

- Make sure the **Aggregator ID** are the same on the ports with the same Port Channel configured.
- Bonding Mode is 802.3ad.
- Aggreator ID 號碼在主機重啟後會自行改變。

> If you run into the issue with *Multiple LACP bonds have the same Aggregator ID*, check the link, [https://access.redhat.com/solutions/2916431](https://access.redhat.com/solutions/2916431) .

```
[root@tpeitptsm01 ~]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer2 (0)
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0

802.3ad info
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: b4:7a:f1:4c:8b:1c
Active Aggregator Info:
        Aggregator ID: 1           <==== 所有 port 必須是同一個 ID，這也表示是同一個 portchannel.
        Number of ports: 4         <==== 這個 portchannel 有幾個 port
        Actor Key: 9
        Partner Key: 3
        Partner Mac Address: 70:18:a7:dc:ac:80

Slave Interface: eno1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: b4:7a:f1:4c:8b:1c
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none  <===
Actor Churned Count: 0
Partner Churned Count: 0   <===
details actor lacp pdu:
    system priority: 65535
    system mac address: b4:7a:f1:4c:8b:1c
    port key: 9
    port priority: 255
    port number: 1
    port state: 61
details partner lacp pdu:
    system priority: 32768
    system mac address: 70:18:a7:dc:ac:80   <===
    oper key: 3
    port priority: 32768
    port number: 263
    port state: 61

Slave Interface: eno2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: b4:7a:f1:4c:8b:1d
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
    system priority: 65535
    system mac address: b4:7a:f1:4c:8b:1c
    port key: 9
    port priority: 255
    port number: 2
    port state: 61
details partner lacp pdu:
    system priority: 32768
    system mac address: 70:18:a7:dc:ac:80
    oper key: 3
    port priority: 32768
    port number: 264
    port state: 61


```

#### Configure Switch

[![rhel_network_bonding_switch_config.png](http://www.osslab.tw/uploads/images/gallery/2021-11/scaled-1680-/rhel_network_bonding_switch_config.png)](http://www.osslab.tw/uploads/images/gallery/2021-11/rhel_network_bonding_switch_config.png)

#### Ubuntu with netplan  


- [A Beginner’s Guide to Creating Network Bonding and Bridging in Ubuntu](https://www.tecmint.com/create-network-bond-bridge-in-ubuntu/)