Problem with aggregate NICs via netplan with fstab.
by boyturtle from LinuxQuestions.org on (#5ESW6)
I'm running Kubuntu 20.04 and have had server shares mounted on my desktop with /etc/fstab for some time now and all has been working well, without issue.
Recently, I decided to aggregate the 2 NICs I have in my pc with netplan, my chosen mode was 802.3ad and my Unifi switch supports this. However, as I am new to netplan, this has been quite challenging, but I finally got it to work and the 2 cards were running. Unfortunately, I lost the drives that were previously mounted in /etc/fstab following a restart (but they do still work in the time after I run the command sudo netplan apply and before restarting the pc)
I'm sure mounted disks and aggregated NICs should happily live side by side, so I'm wondering if something in the code I'm using is causing this problem or if I've gone about this the wrong way.
A typical line in the /etc/fstab is
Code://192.168.52.170/Admin /home/ServerAdmin cifs vers=1.0,uid=boyturtle,gid=boyturtle,credentials=/home/boyturtle/.smbcredentials,iocharset=utf8 0 0The full netplan yaml file is as follows
Code:network:
version: 2
renderer: NetworkManager
ethernets:
enp3s0:
dhcp4: no
enp0s31f6:
dhcp4: no
bonds:
bond0:
interfaces: [enp3s0, enp0s31f6]
addresses: [192.168.52.128/24]
gateway4: 192.168.52.101
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 1
nameservers:
addresses:
- 192.168.52.101
- 1.1.1.1
- 9.9.9.9I understand that indentations are critical in yaml file, but I guess mine are correctly formatted as I believe the aggregation worked. The output (before restart, if it matters) for cat /proc/net/bonding/bond0 gave me
Code:Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer3+4 (1)
MII Status: up
MII Polling Interval (ms): 1
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
Slave Interface: enp0s31f6
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 70:85:c2:66:ec:9a
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 0
Partner Churned Count: 0
Slave Interface: enp3s0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 70:85:c2:66:ec:98
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 0
Partner Churned Count: 0The ouput (again, before restart) for ethtool bond0 gave me
Code:Settings for bond0:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 2000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Cannot get wake-on-lan settings: Operation not permitted
Link detected: yesCan anyone suggest a way forward to get this working properly?
Recently, I decided to aggregate the 2 NICs I have in my pc with netplan, my chosen mode was 802.3ad and my Unifi switch supports this. However, as I am new to netplan, this has been quite challenging, but I finally got it to work and the 2 cards were running. Unfortunately, I lost the drives that were previously mounted in /etc/fstab following a restart (but they do still work in the time after I run the command sudo netplan apply and before restarting the pc)
I'm sure mounted disks and aggregated NICs should happily live side by side, so I'm wondering if something in the code I'm using is causing this problem or if I've gone about this the wrong way.
A typical line in the /etc/fstab is
Code://192.168.52.170/Admin /home/ServerAdmin cifs vers=1.0,uid=boyturtle,gid=boyturtle,credentials=/home/boyturtle/.smbcredentials,iocharset=utf8 0 0The full netplan yaml file is as follows
Code:network:
version: 2
renderer: NetworkManager
ethernets:
enp3s0:
dhcp4: no
enp0s31f6:
dhcp4: no
bonds:
bond0:
interfaces: [enp3s0, enp0s31f6]
addresses: [192.168.52.128/24]
gateway4: 192.168.52.101
parameters:
mode: 802.3ad
transmit-hash-policy: layer3+4
mii-monitor-interval: 1
nameservers:
addresses:
- 192.168.52.101
- 1.1.1.1
- 9.9.9.9I understand that indentations are critical in yaml file, but I guess mine are correctly formatted as I believe the aggregation worked. The output (before restart, if it matters) for cat /proc/net/bonding/bond0 gave me
Code:Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer3+4 (1)
MII Status: up
MII Polling Interval (ms): 1
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
Slave Interface: enp0s31f6
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 70:85:c2:66:ec:9a
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 0
Partner Churned Count: 0
Slave Interface: enp3s0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 70:85:c2:66:ec:98
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 0
Partner Churned Count: 0The ouput (again, before restart) for ethtool bond0 gave me
Code:Settings for bond0:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: No
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 2000Mb/s
Duplex: Full
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Cannot get wake-on-lan settings: Operation not permitted
Link detected: yesCan anyone suggest a way forward to get this working properly?