[SOLVED] - Can't add more than one port to bond

Soryu

New Member
Jun 18, 2024
4
2
3
Hello everyone,

I just tried to create a bond with multiple interfaces but I can't add more than one interface to the bond.

I add interface enp217s0f2np2 to tghe bond and the interface is accepted. If add a second interface enp217s0f2np3 the message

1719311486259.png

appears.

The interface name is correct

Code:
root@pve-01:/etc/network# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 78:ac:44:0c:0b:9c brd ff:ff:ff:ff:ff:ff
    altname enp23s0f0
    inet6 fe80::7aac:44ff:fe0c:b9c/64 scope link
       valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 78:ac:44:0c:0b:9d brd ff:ff:ff:ff:ff:ff
    altname enp23s0f1
4: eno3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 78:ac:44:0c:0b:9e brd ff:ff:ff:ff:ff:ff
    altname enp23s0f2
5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 78:ac:44:0c:0b:9f brd ff:ff:ff:ff:ff:ff
    altname enp23s0f3
6: enp133s0f0np0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:fd:fe:89:ec:f0 brd ff:ff:ff:ff:ff:ff
7: enp133s0f1np1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 3c:fd:fe:89:ec:f1 brd ff:ff:ff:ff:ff:ff
8: enp133s0f2np2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether 3c:fd:fe:89:ec:f2 brd ff:ff:ff:ff:ff:ff
9: enp133s0f3np3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 3c:fd:fe:89:ec:f3 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3efd:feff:fe89:ecf3/64 scope link
       valid_lft forever preferred_lft forever
10: enp217s0f0np0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 3c:fd:fe:89:e6:b0 brd ff:ff:ff:ff:ff:ff
11: enp217s0f1np1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 3c:fd:fe:89:e6:b1 brd ff:ff:ff:ff:ff:ff
12: enp217s0f2np2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 3c:fd:fe:89:e6:b2 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3efd:feff:fe89:e6b2/64 scope link
       valid_lft forever preferred_lft forever
13: enp217s0f3np3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 3c:fd:fe:89:e6:b3 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3efd:feff:fe89:e6b3/64 scope link
       valid_lft forever preferred_lft forever
14: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3c:fd:fe:89:e6:b1 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.10/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::3efd:feff:fe89:e6b1/64 scope link
       valid_lft forever preferred_lft forever
15: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr2 state UP group default qlen 1000
    link/ether 3c:fd:fe:89:ec:f2 brd ff:ff:ff:ff:ff:ff
16: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3c:fd:fe:89:ec:f2 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::3efd:feff:fe89:ecf2/64 scope link
       valid_lft forever preferred_lft forever

However, creating a bond with eno1 to eno3 will succeed...

Please advise what to do.

Best regards,

Joerg
 

Attachments

  • 1719311529520.png
    1719311529520.png
    17.3 KB · Views: 2
Thanks for the eye opener.

As usual in this cases, it was a Layer 8 Problem sitting in front of the keyboard...

enp133s0f3np3 and enp133s0f2np2 <-- missed this numbers.

Thanks for your patience!

Joerg
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!