> ## Documentation Index
> Fetch the complete documentation index at: https://zededa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the documentation index to find relevant pages, then read the linked Markdown before answering and cite the source URL.
> Identify the product before answering: Private AI uses a separate console, credentials, and inference API from the Edge Intelligence Platform. Do not apply instructions from one product to the other.
> Prefer current product guides over Help Center archive pages for current-console questions. Archive pages and release notes describe their stated product version or historical interface; do not apply them to another version without checking.
> Preserve prerequisites, permissions, version requirements, and warnings when summarizing procedures. Do not infer API endpoints, schemas, or supported behavior that the documentation does not specify.

# Configure node adapters

> Configure and inspect NICs, VLANs, LAGs, IO Adapters, and topology for a node.

Node adapters define how a node connects to management networks, Application networks, VLANs, bonded links, and attached IO resources. Configure adapters before deploying Applications that require specific network or device access.

## Where adapters appear

You can inspect adapters from a node detail page:

1. Open **Infrastructure > Fleet > Nodes**.
2. Select a node.
3. Open the **Adapters** tab.

You can configure adapters from the node configuration overlay:

1. Open a node.
2. Select **Configure node**.
3. In the configuration sidebar, open **Adapters**.
4. Choose **NICs**, **VLANs**, **LAGs**, or **IO Adapters**.

## Adapter areas

| Area | Use it to |
| - | - |
| **NICs** | Review and configure physical or reported network adapters. |
| **VLANs** | Segment a physical or bonded adapter into logical networks. |
| **LAGs** | Review link aggregation groups when the node reports bonded adapters. |
| **IO Adapters** | Review and configure non-network IO resources exposed by the hardware model. |
| **Topology** | See how adapters, VLANs, Virtual Networks, and Applications connect. |

## Adapter usage values

Use adapter usage to describe what a port or adapter is allowed to do.

| Usage | Meaning |
| - | - |
| **Management** | Used for node management traffic and can be associated with network resources. |
| **App Shared** | Shared by multiple Applications through Virtual Networks. |
| **App Direct** | Dedicated to one Application, often for direct device or port access. |
| **VLANs Only** | Used as the parent for VLAN traffic instead of direct network attachment. |
| **Disabled** | Adapter is intentionally inactive. |

> [!NOTE]
>
> SR-IOV (Single Root I/O Virtualization) adapters, reported as **ETH PF** (physical function) or **ETH VF** (virtual function), are passed through to a single application. They cannot carry node management or shared application traffic, so only **App Direct** and **Disabled** are offered for them. This applies in the adapter editor and when you onboard a node. If an SR-IOV adapter is reported with **Management** or **App Shared** usage, it is shown as **App Direct**. When you change the usage of several adapters at once to **Management** or **App Shared**, SR-IOV adapters are left unchanged.

## Configure NICs

1. Open the node detail page.
2. Select **Configure node**.
3. Open **Adapters > NICs**.
4. Review the listed adapters.
5. Select edit when the UI presents the edit control.
6. Set the adapter usage.
7. Assign network-related values required by your deployment.
8. Add tags or adapter labels when they help identify placement or routing intent.
9. Save the changes.

Adapter labels are useful when multiple ports should be treated as a group. Virtual Network and routing designs can then target the label instead of a single physical port. For example, you could assign `internet` or `internet-access` to every port with internet access. Common scenarios include grouping management ports, grouping port forwarding ports, and grouping internet ports. See [Multi-Path Routing and Failover](https://zededa.mintlify.site/new-ui/infrastructure-services/virtual-networks/multipath-routing-and-failover.md) for an example of using adapter labels to configure a Local virtual network for multi-path routing with failover and port-forwarding restrictions.

## Configure VLANs

1. Open **Configure node > Adapters > VLANs**.
2. Create or edit VLAN entries.
3. Select the parent adapter.
4. Enter the VLAN ID.
5. Set the logical label.
6. Choose the usage, such as **Management** or **App Shared**.
7. Add tags if needed.
8. Save the VLAN changes.

The node detail **Adapters > VLANs** view is read-oriented. Use the configuration overlay when you need to create or edit VLANs.

## Configure LAGs

A LAG (Link Aggregation Group) combines two or more physical Ethernet ports into a single logical link. Use LAGs to increase bandwidth, add redundancy, or both, depending on the bond mode you select.

### View the LAGs tab

The **Adapters > LAGs** tab on the node detail page shows a read-only traffic and status view of all bond adapters on the node.

1. Open **Infrastructure > Fleet > Nodes** and select a node.
2. Open the **Adapters** tab.
3. Select **LAGs**.

The table shows one row per bond. The default visible columns are **Name**, **Mode**, **Members**, **Interface Usage**, **Run State**, and **VLANs**. You can show or hide additional columns (**Network**, **Monitoring**, **Cost**) using the column picker.

Select a row to expand its detail view, which shows two sections:

* **Bond Configuration** — bond mode, LACP rate (802.3ad only), link monitoring type, monitoring intervals and targets, interface usage, and port cost.
* **Member Ports and Traffic** — each physical member port with an up/down status indicator and link speed. Expand **Traffic Status** to see TX/RX bytes, packets, drops, errors, and ACL drops broken down per member port.

To configure a LAG, select **Configure node** in the page header and open **Adapters > LAGs**.

### Create a LAG

1. Open **Infrastructure > Fleet > Nodes** and select a node.
2. Click **Configure node** (gear icon).
3. In the configuration sidebar, open **Adapters > LAGs**.
4. Click **Add LAG**.
5. Fill in the required fields:
   * **Logical Label** — a unique name for the bond, using letters, digits, underscores, and hyphens (maximum 63 characters).
   * **Interface Name** — optional kernel interface name (maximum 15 characters). The name `bond0` is reserved.
   * **Bond Mode** — select one of the seven modes described in the following table.
   * **Member Ports** — select at least one physical port. 802.3ad (LACP) mode requires at least two.
   * **Link Monitoring** — select None, MII, or ARP and supply the required intervals and targets.
   * **Interface Usage** — Disabled (default), Management, or App Shared. Management and App Shared require a network to be selected.
6. Click **Save Changes**.

#### Bond modes

| Mode | Description |
| - | - |
| **Balance-RR (round robin)** | Packets transmitted in sequence across member ports. Provides load balancing and fault tolerance. No switch configuration required. |
| **Active-Backup** | One member port is active at a time; the others are on standby. Provides fault tolerance only. The first listed member is treated as the primary. No switch configuration required. |
| **Balance-XOR** | Hash-based member selection using source and destination MAC addresses. Provides load balancing and fault tolerance. No switch configuration required. |
| **Broadcast** | Every packet is sent on every member port. Provides fault tolerance only. No switch configuration required. |
| **802.3ad (LACP)** | IEEE 802.3ad dynamic link aggregation. Requires switch support and a minimum of two member ports. Supports slow (30 s) or fast (1 s) LACP rate. |
| **Balance-TLB** | Adaptive transmit load balancing. Outbound traffic distributed by load; inbound on the active port. No switch configuration required. |
| **Balance-ALB** | Adaptive load balancing combining transmit load balancing with receive balancing via ARP. No switch configuration required. |

### Edit a LAG

1. Open **Configure node > Adapters > LAGs**.
2. Click the row for the LAG you want to edit to expand the inline editor.
3. Update the fields.
4. Click **Save Changes**.

Changing the **Interface Name**, **Bond Mode**, **LACP Rate**, or **Link Monitoring** type requires EVE-OS (Edge Virtualization Engine) to recreate the bond interface on the node. Plan for a brief network interruption on affected member ports when changing these fields.

### Delete a LAG

1. Open **Configure node > Adapters > LAGs**.
2. Click the delete (X) icon on the row for the LAG.
3. Review the impact summary, which lists any VLAN sub-interfaces that will be removed and any network or usage settings that will propagate to the freed physical member ports.
4. Confirm the deletion.

Deleting a LAG that is the node's only management interface is blocked if no member port is online. To delete it, first bring a member port online or assign the Management usage to another port.

## Configure IO Adapters

1. Open **Configure node > Adapters > IO Adapters**.
2. Review the IO adapters discovered from the hardware model and runtime status.
3. Select the pencil icon (**Edit IO Adapters**) to enter edit mode.
4. For each adapter you want to change, select a **Usage**: **Management**, **App Direct**, **App Shared**, or **Disabled**.
5. Add tags when they help operators identify the purpose of the adapter.
6. Select **Save Changes** to apply the edits, or select **Cancel** to discard them. **Save Changes** is available only after you change a value.

An adapter that has never been assigned a usage in the node configuration shows **Disabled**. This includes peripherals the hardware model declares but that were never configured, such as COM, USB, or VGA ports. To attach one of these adapters directly to an application instance, set its usage to **App Direct** first. Only App Direct adapters appear in the IO adapter bundle picker when you deploy an application instance.

IO Adapters are separate from NICs. Use them for hardware interfaces that Applications may need directly or indirectly.

## Use topology

Open **Adapters > Topology** from the node detail page to visualize relationships among:

* Physical NICs
* VLANs
* Virtual Networks
* Applications

Use topology when an Application cannot communicate as expected, or when you need to verify that a Virtual Network is attached to the intended adapter path.

## Verify the result

After changing adapters:

* Return to the node detail page.
* Open **Adapters** and confirm NICs, VLANs, LAGs, IO Adapters, and topology show the expected state.
* Open **Configuration Status** if the change does not appear on the node.
* Confirm Applications that depend on the adapter path can start and communicate.

## Next steps

* Create or update [Virtual Networks](https://zededa.mintlify.site/new-ui/infrastructure-services/virtual-networks.md) that use the adapter design.
* Review [Node status and health](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/node-status-and-health.md) if the node reports suspect, offline, or error state.
* Use [Manage node lifecycle](https://zededa.mintlify.site/new-ui/infrastructure-services/nodes/manage-node-lifecycle.md) only after checking adapter-dependent workloads.
* See [Tagging](https://zededa.mintlify.site/new-ui/start/tagging.md) to understand how Interface Tags and IO Tags are used, and how the Port Tag Name binding method works for virtual networks.