Page MenuHomeVyOS Platform
Create Task
Maniphest T4976

Unable to form bond with Broadcom Inc. BCM57454 NetXtrem-E
Open, WishlistPublicBUG
Actions

Description

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.

Details

Difficulty level
Unknown (require assessment)
Version
VyOS 1.3-rolling-202301311151
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Bug (incorrect behavior)

Event Timeline

ghavag created this task.Feb 3 2023, 3:41 PM
ghavag updated the task description. (Show Details)Feb 3 2023, 3:51 PM
pasik added a subscriber: pasik.Feb 3 2023, 4:32 PM
syncer edited projects, added VyOS 1.3 Equuleus (1.3.5); removed VyOS 1.3 Equuleus.Aug 27 2023, 12:09 AM
syncer edited projects, added VyOS 1.3 Equuleus (1.3.6); removed VyOS 1.3 Equuleus (1.3.5).Dec 17 2023, 11:36 PM
Viacheslav triaged this task as Wishlist priority.Jan 20 2024, 11:38 AM
Viacheslav edited projects, added VyOS 1.5 Circinus; removed VyOS 1.3 Equuleus (1.3.6).
Viacheslav added a subscriber: Viacheslav.

@ghavag Does it work for 1.5?

ghavag added a comment.Feb 26 2024, 12:24 PM

@Viacheslav the problem was still solved in 1.4. (I don't know, when I will have the chance to test with 1.5.) The reason this issue exists is, that 1.4. was not declared to be stable back then. Now since 1.4 is official released as stable we can use 1.4 instead of 1.3. So I think we can close the issue.