Now let’s examine the bond connection: $ cat work Next, we add the device’s details in the Bond section. So in the NetDev section, we define the type and name of the device. Now, let’s review the setup: $ ls -1 /etc/systemd/networkįirst, let’s look into the bond device: $ cat dev So per convention, we should start their names with numbers. Let’s notice that the files are parsed in alphabetic order. In addition, the Permanent HW addr contains the MAC address of each slave interface before bonding. We can find that the currently used slave link is enp0s3. Primary Slave: enp0s3 (primary_reselect always) Now let’s check the bonding configuration in the /proc/net/bonding/nm-bond file: $ cat /proc/net/bonding/nm-bondĮthernet Channel Bonding Driver: v5.15.0-47-genericīonding Mode: fault-tolerance (active-backup) Moreover, let’s notice that the MAC address of all three interfaces is the same. So we can find out that the bonding is working with two slaves.
Link/ether 6a:23:45:28:ac:0f brd ff:ff:ff:ff:ff:ff permaddr 08:00:27:fa:13:16Ĥ: nm-bond: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 Link/ether 6a:23:45:28:ac:0f brd ff:ff:ff:ff:ff:ff permaddr 08:00:27:42:6c:e3ģ: enp0s8: mtu 1500 qdisc fq_codel master nm-bond state UP mode DEFAULT group default qlen 1000
Let’s reboot the system and check the links: $ ip linkġ: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
0 kommentar(er)
