Op 31-07-2023 om 11:57 schreef Curious Pandora:
Thanks for the reply. For some strange reason cloudstack agent doesn't
work with the bridge interfaces that the vnis are attached to.
But how did you connect them? For each VNI CloudStack should create a
separate bridge on the fly. That's done by that modifyvxlan.sh script.
Is the broadcast domain for the network set to vxlan://1234 where 1234
is your VNI ID?
Wido
From the management server:
Failed to handle host connection:
com.cloud.exception.ConnectionException: Incorrect Network setup on
agent, Reinitialize agent after network names are setup, details : Can
not find network: brguestl2
From the host side:
bridge name bridge id STP enabled interfaces
brguestl2 8000.a2d96b610d2a no vniguestl2
On Mon, Jul 31, 2023 at 12:10 PM Wido den Hollander <[email protected]
<mailto:[email protected]>> wrote:
Op 31/07/2023 om 10:03 schreef Curious Pandora:
> Hello,
>
> just a quick confirmation if the VXLAN plugin can apply to
> management/storage/public networks as well or is only implemented
for guest
> networks.
>
Keep in mind that the 'plugin' is just a Shell script (modifyvxlan.sh)
which is executed upon VM launch.
All it does is create some Linux bridges and VXLAN interfaces
on-demand,
but that's it.
If you want to work with VXLAN you will probably have to do some work
manually on the hypervisors to get BGP and EVPN working as well.
For mgmt and storage traffic you could then use systemd-networkd to
create VXLAN devices where needed.
That's how I do it :-)
Wido
> Kind regards,
>
>
--
p4nd0ra - the curious
