Change Details

With VyOS 1.3., even with the latest rolling, e.g. 202301311151, it is not possible to form a network bond using Broadcom Inc. BCM57454 NetXtrem-E NIC. The interfaces work in non-bond but as soon as a bond is created the member interfaces will be marked as down and it it not possible to bring them up again expect by deleting the bond. The following minimal example is sufficient to reproduce the problem: ``` set interface bonding bond0 mode 802.3ad set interface bonding bond0 member interface eth2 set interface bonding bond0 member interface eth3 commit ``` After issuing those commands the following output is shown on the screen: ``` [ 562.289475] bnxt_en 0000:18:00.0 eth2: NIC Link is Down [ 562.529188] bnxt_en 0000:18:00.1 eth3: NIC Link is Down ``` The problem is reproducible even with only one bond member and a mode other that 802.3ad.

With VyOS 1.3., even with the latest rolling, e.g. 202301311151, it is not possible to form a network bond using Broadcom Inc. BCM57454 NetXtrem-E NIC. The interfaces work in non-bond but as soon as a bond is created the member interfaces will be marked as down and it it not possible to bring them up again. Is reboot is required to bring them up again. The following minimal example is sufficient to reproduce the problem: ``` set interface bonding bond0 mode 802.3ad set interface bonding bond0 member interface eth2 set interface bonding bond0 member interface eth3 commit ``` After issuing those commands the following output is shown on the screen: ``` [ 562.289475] bnxt_en 0000:18:00.0 eth2: NIC Link is Down [ 562.529188] bnxt_en 0000:18:00.1 eth3: NIC Link is Down ``` The problem is reproducible even with only one bond member and a mode other that 802.3ad.

With VyOS 1.3., even with the latest rolling, e.g. 202301311151, it is not possible to form a network bond using Broadcom Inc. BCM57454 NetXtrem-E NIC. The interfaces work in non-bond but as soon as a bond is created the member interfaces will be marked as down and it it not possible to bring them up again expect by delet. Is reboot is required to bring the bondm up again. The following minimal example is sufficient to reproduce the problem: ``` set interface bonding bond0 mode 802.3ad set interface bonding bond0 member interface eth2 set interface bonding bond0 member interface eth3 commit ``` After issuing those commands the following output is shown on the screen: ``` [ 562.289475] bnxt_en 0000:18:00.0 eth2: NIC Link is Down [ 562.529188] bnxt_en 0000:18:00.1 eth3: NIC Link is Down ``` The problem is reproducible even with only one bond member and a mode other that 802.3ad.