Skip to main content
Version: 0.0.15 (latest)

Network Concepts

Hardware → Network is a single page covering the cluster's network configuration.

PanelWhat it shows
Fabric ProtocolThe cluster's storage transport — RDMA or TCP
Service EndpointsControl-plane and data-plane endpoints with their status and bandwidth
Port SettingsThe external host ports for the Dashboard and Manager API
Subnet OverviewConfigured subnets with their per-node interface assignments
Unassigned InterfacesPorts not bound to any subnet
Storage Access PointsWhich IPs serve as storage access points
Storage Data PlaneWhich NIC each storage node uses for I/O traffic

Interfaces

Every network port detected across all nodes is listed with its node, interface name, speed, IP, roles, status, and MAC address. Ports that are link-down or not bound to a subnet are shown too:

StatusMeaning
UpLink up and in use
DownLink down
UnknownLink state not reported
UnusedNot bound to any subnet — assign it under Subnets

IP Roles

Each assigned IP carries one or more roles:

RolePurpose
ManagerServes the Manager REST API and the Dashboard
Storage ControlStorage control plane — the management service endpoint. Changing it triggers a rolling restart.
Storage DataCarries storage I/O traffic
ReplicationCarries replication traffic

Subnets

A subnet is a logical network segment with per-node interface assignments.

FieldDescription
NameHuman-readable identifier
EnabledWhether the subnet is active
PrefixNetwork address in CIDR notation, e.g. 192.168.10.0/24
VLANOptional VLAN ID (0–4094). Leave empty for no VLAN tagging.
GatewayDefault gateway for this subnet. A fabric subnet may have no gateway.
MTUMaximum transmission unit in bytes, up to 9000
Interface AssignmentsPer-node mapping of interface to IP address in CIDR form

A single physical network can carry every kind of traffic, or you can separate them onto dedicated subnets for isolation and performance.

info

Static fabric and management addresses configured for a node persist across reboots.