Current setup:
- 6-node MicroCloud cluster (LXD 5.21.4 LTS, MicroOVN)
- Single copper NIC per host for WAN, all connected to a DMZ switch
- One ISP-provided router on the switch
- One physical uplink network
UPLINK(parent=eno8403) → one OVN network default - Network forwards on
defaultroute public IPs to containers
Goal:
- Connect a second ISP-provided router to the same DMZ switch
- Create
UPLINK2→ovn2with its own network forwards - Peer routing between
ovn2anddefaultso forwards onovn2reach containers ondefault - Motivation: traffic peaks approach 1 Gbit/s on the single WAN link. With two uplinks on separate chassis, we’d get 2 Gbit/s aggregate.
Problem:
Both /29 subnets are flat on the same L2 (same physical NIC, same switch). UPLINK already claims eno8403 as parent, so creating UPLINK2 with the
same parent fails the duplicate-parent check.
Options we see:
- Set
UPLINK2parent tolxdovn1(the existing OVS provider bridge) — bypasses the check since it’s a different string. Can’t find anyone doing this. - Managed switch with VLANs — tag each subnet, use
vlan=onUPLINK2. Supported, but requires replacing our unmanaged switch.
Is (1) viable? Is there a better way?