Bond/AE and VLAN Interfaces

Bond group supports combinations of interface type, data network type, and vSwitch type.

OVS (Kernel Datapath)

With OVS kernel, the Neutron OVS agent is able to create bridge at runtime. The interface’s OS device name is added as a port to an auto-created br-phy<N> bridge.

Interface Type

Flat Datanet

VLAN Datanet

Ethernet

Y

Y

Bond/Aggregated Ethernet

Y

Y

VLAN

Y

N

  • VLAN interface + flat data network: Supported since release r12. Each VLAN sub-interface gets its own OVS bridge (br-phy<N>), with the OS VLAN device (example: vlan#100) used as the bridge port. This allows multiple VLAN interfaces to share the same physical port with each interface mapped to a separate flat provider network without port conflicts.

  • VLAN interface + vlan data network: A VLAN type data network cannot be assigned to a VLAN interface. This prevents double-VLAN-tagging conflicts where the outer tag is managed by the kernel VLAN device and the inner tag is managed by Neutron.

    This combination is not supported by StarlingX.

  • VLAN interface + vxlan data network: VXLAN data-networks on VLAN interfaces are not a validated configuration. VXLAN requires an IP address on the data interface for tunnel endpoints, and this topology adds complexity. Use an ethernet or AE interface for VXLAN data networks.

SR-IOV and PCI Passthrough

SR-IOV and PCI passthrough interfaces are handled by the Neutron SR-IOV agent and not by OVS. They generate physical_device_mappings entries that map data network names to the physical device names.

Interface Type

Flat Datanet

VLAN Datanet

pci-sriov

Y

Y

pci-passthrough

Y

Y

Note

  • Each SR-IOV interface is limited to one data-network.

  • VXLAN is not applicable to SR-IOV or PCI passthrough interfaces, as it bypasses the vSwitch entirely.