Skip to content

Network Design

Each bare-metal node has four 25GbE NICs bonded into a single LACP aggregate using 802.3ad mode. Traffic is carried on VLAN 111 (native/untagged at the switch) on a /24 subnet. Because VLAN 111 is the native VLAN, no VLAN sub-interface is needed -- the IP address is assigned directly to the bridge interface (br0).

NIC Inventory

Each bare-metal node (Supermicro NX-8150-G7 chassis) has four 25GbE Ethernet ports:

Interface Name Slot Speed Purpose
enp134s0f0np0 PCIe Slot 1, Port 0 25GbE LACP bond member
enp134s0f0np1 PCIe Slot 1, Port 1 25GbE LACP bond member
enp175s0f0np0 PCIe Slot 2, Port 0 25GbE LACP bond member
enp175s0f0np1 PCIe Slot 2, Port 1 25GbE LACP bond member

NIC Naming

Interface names were discovered during the initial generic ISO boot on April 29, 2026. These names are hardware-specific to the Supermicro motherboard in the NX-8150-G7 chassis. The names follow the systemd predictable naming scheme based on PCIe bus/slot/function.

Bond Configuration

All four NICs are aggregated into a single LACP bond:

Parameter Value
Bond Name bond0
Mode 802.3ad (LACP)
LACP Rate fast (1 second)
Transmit Hash layer3+4 (balance-tcp)
MII Monitor Interval 100ms
Member Interfaces enp134s0f0np0, enp134s0f0np1, enp175s0f0np0, enp175s0f0np1

VLAN Configuration

Parameter Value
VLAN ID 111
Subnet 10.25.233.0/24
Gateway 10.25.233.254
DNS 10.213.129.245
NTP 10.53.12.18 / ntp.services.glb.toyota.com

Native VLAN

VLAN 111 is configured as the native (untagged) VLAN on the switch ports. No VLAN tagging is needed at the node level.

Network Stack

The network stack follows this architecture on each node:

graph TB
    NIC1["enp134s0f0np0"] --> BOND["bond0<br/>802.3ad LACP"]
    NIC2["enp134s0f0np1"] --> BOND
    NIC3["enp175s0f0np0"] --> BOND
    NIC4["enp175s0f0np1"] --> BOND
    BOND --> BR["br0<br/>Linux Bridge<br/>10.25.233.x/24"]

Stack summary: NICs --> bond0 (LACP 802.3ad) --> br0 (bridge, IP assigned directly -- VLAN 111 is native/untagged)

systemd-networkd Configuration

The appliance mode ISO bakes these network configurations into each node. The following systemd-networkd files are generated during the CanvOS build and applied at install time.

NetDev: Bond

10-bond0.netdev
[NetDev]
Name=bond0
Kind=bond

[Bond]
Mode=802.3ad
LACPTransmitRate=fast
TransmitHashPolicy=layer3+4
MIIMonitorSec=100ms

Network: NIC Members

10-enp134s0f0np0.network
[Match]
Name=enp134s0f0np0

[Network]
Bond=bond0
10-enp134s0f0np1.network
[Match]
Name=enp134s0f0np1

[Network]
Bond=bond0
10-enp175s0f0np0.network
[Match]
Name=enp175s0f0np0

[Network]
Bond=bond0
10-enp175s0f0np1.network
[Match]
Name=enp175s0f0np1

[Network]
Bond=bond0

NetDev: Bridge

20-br0.netdev
[NetDev]
Name=br0
Kind=bridge

[Bridge]
STP=false
ForwardDelaySec=0

Network: Bond to Bridge

20-bond0.network
[Match]
Name=bond0

[Network]
Bridge=br0

Network: Bridge Address (per-node)

Each node gets a unique IP address assigned directly to br0. This is configured in the per-node site-user-data ISO. Because VLAN 111 is native/untagged, no VLAN sub-interface is needed.

30-br0.network
[Match]
Name=br0

[Network]
Address=10.25.233.4/24
Gateway=10.25.233.254
DNS=10.213.129.245
NTP=10.53.12.18

[Route]
Gateway=10.25.233.254
Destination=0.0.0.0/0
30-br0.network
[Match]
Name=br0

[Network]
Address=10.25.233.5/24
Gateway=10.25.233.254
DNS=10.213.129.245
NTP=10.53.12.18

[Route]
Gateway=10.25.233.254
Destination=0.0.0.0/0
30-br0.network
[Match]
Name=br0

[Network]
Address=10.25.233.6/24
Gateway=10.25.233.254
DNS=10.213.129.245
NTP=10.53.12.18

[Route]
Gateway=10.25.233.254
Destination=0.0.0.0/0

IP Addressing

Node Hostname IP Address Role
Node 1 STG-WAHVP004 10.25.233.4 Control plane + worker
Node 2 STG-WAHVP005 10.25.233.5 Control plane + worker
Node 3 STG-WAHVP006 10.25.233.6 Control plane + worker
Palette VIP -- 10.25.232.155 Palette Management Appliance VIP
Palette Node -- 10.25.232.252 Palette Management Appliance node IP

Switch Requirements

The upstream switch ports must be configured for:

  • LACP (802.3ad) on all 4 ports per node (12 ports total for 3 nodes)
  • VLAN 111 trunked or native on the port channel
  • Jumbo frames (MTU 9000) recommended for Portworx replication traffic
  • Spanning Tree PortFast or edge port on all node-facing ports

Portworx Network

All Portworx inter-node traffic (ports 9001-9022) runs on the same VLAN 111 subnet. No separate storage network or VLAN is required for the POC. Portworx replication uses the node IP addresses directly.