I believe they updated the vdsm configuration part.
You just need to configure the bond on the host via the cockpit.
For some reason, I needed to configure an IP on the bond, otherwise the bond
kept deactivating and I lost connection with the host.
Then, you create the vlan interface on top of th
> For the ovirtmgmt there’s some caveats to add it on top of bonds. I’m not
> sure if as today
> is solved, but you need to preconfigure vdsm if you want the bonded
> interfaces to host
> ovirtmgmt.
Can you please elaborate on the "preconfigure vdsm if you want the bonded
interfaces to host ovi
Ok.
Thanks man!!
I'm working to improve the infrastructure.
Em ter., 27 de jul. de 2021 às 12:23, Vinícius Ferrão <
fer...@versatushpc.com.br> escreveu:
> Yes.
>
> I have it running this way. You must configure as 802.3ad normally on
> oVirt but keep in mind that you must use bond and not teamin
Yes, why not?
k
Sent from my iPhone
> On 27 Jul 2021, at 18:01, Jorge Visentini wrote:
>
>
> Hi all.
>
> Is it possible to configure oVirt for work with two NICs in bond/LACP across
> two switches, according to the image below?
>
>
>
>
> Thank you all.
> You guys do a wonderful job.
>
Yes.
I have it running this way. You must configure as 802.3ad normally on oVirt but
keep in mind that you must use bond and not teaming.
On the switches just configure MLAG, VLT, vPC ou whatever multichassis
aggregation suportes by your switch vendor.
For the ovirtmgmt there’s some caveats to
5 matches
Mail list logo
