Skip to content

Bridge Interface#

Virtual Networks → BIBridge Interfaces

A BridgeInterface combines a single Interface with a VLAN tag to create a sub-interface, which is then connected to a BridgeDomain. This way, the host(s) that are connected to this sub-interface can communicate with other hosts in the BridgeDomain.

BridgeInterface vs VLAN

The BridgeInterface connects a single Interface to the BridgeDomain, while a VLAN uses labels to select which Interfaces are connected to the BridgeDomain. The latter should be preferred wherever possible.

Traffic is switched via the BridgeDomain that matches the VLAN tag that the packets are tagged with, which allows a physical device to communicate with multiple services over the same physical interface.

A common use case is a server that hosts virtual machines: the physical device (hypervisor) hosts multiple VMs, all of which are assigned a unique VLAN ID to be able to connect to the network over the same physical interface.

BridgeInterface graphical representation

An uplink in the context of the BridgeInterface is a connection between a breakout switch and a service-aware switch. The breakout switch usually has fewer capabilities, both in terms of port speeds and control plane functionality.

These switches are typically not VxLAN or MPLS capable, and the distributed BridgeDomain can therefore not be extended onto the access switch. Instead, a separate non-distributed bridge domain service is created on the breakout switch which is attached to the distributed BridgeDomain through the uplink.

The uplinkSelectors label selector property is used to identify which links are connected to breakout switches. The VLAN that is used on this breakout uplink is determined by the uplinkVLANID or uplinkVLANPool property.

Note

On the breakout switch, only the interface selected by the BridgeInterface will be attached to the bridge domain service.

Dependencies#

BridgeDomain#

The BridgeInterface connects an Interface to a BridgeDomain, allowing the hosts that are behind the Interface to communicate with other hosts in the BridgeDomain.

The BridgeDomain must exist before the BridgeInterface can be configured.

Interface#

A BridgeInterface is mapped to a single Interface, although the same Interface can be referenced by many BridgeInterfaces. A VLAN tag is used to determine which service the traffic will be forwarded to.

The Interface must exist before the BridgeInterface can be configured.

Referenced resources#

If an uplink is configured which connects an Interface on a breakout switch to the distributed BridgeDomain service, the uplink label selector selects TopoLink resources that are used to connect the breakout switch to the rest of the network.

Examples#

apiVersion: services.eda.nokia.com/v2
kind: BridgeInterface
metadata:
  namespace: services
  name: hypervisor-11
spec:
  bridgeDomain: stretched-l2
  vlanID: '123'
  interface: dc1-leaf3-ethernet-1-1

cat << 'EOF' | kubectl apply -f -
apiVersion: services.eda.nokia.com/v2
kind: BridgeInterface
metadata:
  namespace: services
  name: hypervisor-11
spec:
  bridgeDomain: stretched-l2
  vlanID: '123'
  interface: dc1-leaf3-ethernet-1-1
EOF

Custom Resource Definition#

To browse the Custom Resource Definition go to crd.eda.dev.

BridgeInterface

services.eda.nokia.com / v2

SPEC

The BridgeInterface enables the attachment of network interfaces to a Bridge Domain. It includes settings for VLAN ID allocation, interface attachment, and actions on ingress and egress traffic. The specification supports integration with other network resources, such as Bridge Domains and Interfaces, and provides advanced features like MAC Duplication Detection with configurable actions.

  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #
  • #

STATUS

  • #
  • #
  • #
  • #
  • #
  • #