From: Uwe Sauter <uwe.sauter.de@gmail.com>
To: Gilberto Ferreira <gilberto.nunes32@gmail.com>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] PVE 7 & LACP
Date: Wed, 21 Jul 2021 17:49:18 +0200 [thread overview]
Message-ID: <d4ee20fa-93ae-1c64-8855-411c7f337fbc@gmail.com> (raw)
In-Reply-To: <CAOKSTBtL9q8ttnxEV8ZtTzNXQp4vRNL7dcqVZ=6iQQ=7O0ZuSw@mail.gmail.com>
Hi Gilberto,
thanks for that tip. Unfortunately the network configuration quits a few steps before the bridge is
configured. The needed bond0 is not created…
Regards,
Uwe
Am 21.07.21 um 17:45 schrieb Gilberto Ferreira:
> Perhaps you need to change or add this feature in the network interface file:
>
> https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Linux_Bridge_MAC-Address_Change
> <https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#Linux_Bridge_MAC-Address_Change>
>
>
>
> ---
> Gilberto Nunes Ferreira
> (47) 99676-7530 - Whatsapp / Telegram
>
>
>
>
>
>
> Em qua., 21 de jul. de 2021 às 12:18, Uwe Sauter <uwe.sauter.de@gmail.com
> <mailto:uwe.sauter.de@gmail.com>> escreveu:
>
> Hi all,
>
> Fresh installation of PVE 7 with all available updates.
>
> It looks like I'm unable to configure bonding of two interfaces using LCAP.
>
> Output from "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 <http://127.0.0.1/8> scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1224 state UP group default
> qlen 1000
> link/ether a4:bf:01:2f:63:f2 brd ff:ff:ff:ff:ff:ff
> altname enp24s0f0
> 3: enp59s0f4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000
> link/ether 00:07:43:18:82:70 brd ff:ff:ff:ff:ff:ff
> inet6 fe80::207:43ff:fe18:8270/64 scope link
> valid_lft forever preferred_lft forever
> 4: enp59s0f4d1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000
> link/ether 00:07:43:18:82:78 brd ff:ff:ff:ff:ff:ff
> inet6 fe80::207:43ff:fe18:8278/64 scope link
> valid_lft forever preferred_lft forever
> 5: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> link/ether a4:bf:01:2f:63:f3 brd ff:ff:ff:ff:ff:ff
> altname enp24s0f1
> 6: ibp94s0: <BROADCAST,MULTICAST> mtu 2044 qdisc noop state DOWN group default qlen 256
> link/infiniband 80:00:0a:08:fe:80:00:00:00:00:00:00:f4:52:14:03:00:2c:14:51 brd
> 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
> 7: ibp94s0d1: <BROADCAST,MULTICAST> mtu 2044 qdisc noop state DOWN group default qlen 256
> link/infiniband 80:00:0a:09:fe:80:00:00:00:00:00:00:f4:52:14:03:00:2c:14:52 brd
> 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
> 8: vmbr1224: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
> qlen 1000
> link/ether a4:bf:01:2f:63:f2 brd ff:ff:ff:ff:ff:ff
> inet 10.224.203.1/16 <http://10.224.203.1/16> scope global vmbr1224
> valid_lft forever preferred_lft forever
> inet6 fe80::a6bf:1ff:fe2f:63f2/64 scope link
> valid_lft forever preferred_lft forever
>
>
> My current /etc/network/interfaces, which is missing the bridges for the VMs:
> auto lo
> iface lo inet loopback
>
> auto eno1
> iface eno1 inet manual
>
> auto enp59s0f4
> iface enp59s0f4 inet manual
> mtu 9000
>
> auto enp59s0f4d1
> iface enp59s0f4d1 inet manual
> mtu 9000
>
> auto bond0
> iface bond0 inet manual
> slaves enp59s0f4 enp59s0f4d1
> bond-downdelay 200
> bond-miimon 100
> bond-mode 802.3ad
> bond-updelay 200
>
> auto vmbr1224
> iface vmbr1224 inet static
> address 10.224.203.1
> netmask 255.255.0.0
> gateway 10.224.200.1
> bridge_ports eno1
> bridge_stp off
> bridge_fd 0
>
> ## # VLAN 155 nativ on bond0
> ## auto vmbr155
> ## iface vmbr155 inet manual
> ## mtu 9000
> ## bridge_ports bond0
> ## bridge_stp off
> ## bridge_fd 0
>
>
> This config was copied over from the PVE 6 installation on the same host which experienced a SSD
> failure and thus was re-installed with PVE 7.
>
>
> Am I missing something? Am I being blind?
>
>
> Any help is appreciated.
>
>
> Thanks,
>
> Uwe
>
>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com <mailto:pve-user@lists.proxmox.com>
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>
>
next prev parent reply other threads:[~2021-07-21 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 15:17 Uwe Sauter
2021-07-21 15:45 ` Gilberto Ferreira
2021-07-21 15:49 ` Uwe Sauter [this message]
2021-07-21 16:41 ` Gilberto Ferreira
2021-07-21 17:31 ` Uwe Sauter
2021-07-21 17:58 ` alexandre derumier
2021-07-21 18:05 ` Uwe Sauter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4ee20fa-93ae-1c64-8855-411c7f337fbc@gmail.com \
--to=uwe.sauter.de@gmail.com \
--cc=gilberto.nunes32@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox