> For the complete documentation index, see [llms.txt](https://docs.vergeos-demo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vergeos-demo.com/run-the-platform/networking/bonded-vlans.md).

# Bonded VLAN-tagged Networks

## Overview

This guide provides instructions for creating an active-backup bond on an External or Maintenance Network. For specific instructions related to bare-metal installations with 2 NICs per node, see the KB article: [Change External Network to Bonded with tagged VLAN](/knowledge-base/networking/change-external-vlan-to-bonded.md).

## Prerequisites

{% hint style="warning" %}
**Before Making Network Changes**

* Verify associated network switch ports are configured for the VLAN tag
* Ensure you have an alternative method to reach the nodes: physical console access or IPMI access
* Confirm the name/password for the "admin" user (user ID #1) Note: The user ID can be found in the URL of the user's dashboard (Key=1 parameter)
  {% endhint %}

## Configuration Steps

### Basic Network Settings

1. Create or edit the network
2. Configure Layer 2 settings:
   * Set Layer 2 Type to vLAN
   * Enter the VLAN ID number in Layer 2 ID field

### Bonding Configuration

1. Enable Bonding by selecting the checkbox
2. Under Bond Interfaces:
   * Select specific core fabric switches (core-fabric-1 Switch, core-fabric-2 Switch) OR
   * Use "All" to select all available interfaces

{% hint style="info" %}

* Selecting specific interfaces provides more control over which NICs are bonded
* The bonded configuration provides network redundancy through active-backup mode, where one NIC remains active while others stand ready as backup
  {% endhint %}

### Additional Network Settings

See KB article: [How to Create an External Network](/knowledge-base/networking/create-external-network.md) for information on configuring other external network options.

## Testing and Verification

### Basic Connectivity Test

1. Verify the network has connectivity using the [Network Diagnostics Tool](/run-the-platform/networking/network-diagnostics.md)
2. Common diagnostic tests include:
   * Ping test to verify basic connectivity
   * DNS lookup to verify name resolution
   * TCP connection test to verify specific port connectivity

### Bond Failover Testing

1. Navigate to the modified network dashboard
2. Select NICs to view the network adapters
3. Test failover:
   * Physically disconnect one of the associated network cables
   * UI should indicate the disconnected NIC is in "Down" status
   * Verify network maintains connectivity through the backup NIC

{% hint style="warning" %}
**Important**

Before disconnecting any network cable, verify:

* It is not a core network cable OR
* Proper core network redundancy is in place
  {% endhint %}

## Troubleshooting

If you encounter issues:

1. Verify switch configuration matches VLAN settings
2. Check physical cable connections
3. Confirm bond interface selections are correct
4. Review network logs for error messages
5. Test connectivity from multiple points in the network

## Related Articles

* [How to Create an External Network](/knowledge-base/networking/create-external-network.md)
* [Change External Network to Bonded with tagged VLAN](/knowledge-base/networking/change-external-vlan-to-bonded.md)
* [Network Diagnostics Tool](/run-the-platform/networking/network-diagnostics.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vergeos-demo.com/run-the-platform/networking/bonded-vlans.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.