> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/functionality/autodiscovery-multilink.md).

# Autodiscovery - Multilink

## Overview

Highlight can discover switch interfaces bonded using LACP (Link Aggregation Control Protocol - a protocol for the bundling multiple physical ports that can be then be treated as a single channel for network traffic purposes) or PAgP (Port Aggregation Protocol - a protocol for the bundling multiple physical ports that can be then be treated as a single channel for network traffic purposes), and also bonded WAN interfaces built using PPP (Point-to-Point Protocol - a data link (layer 2) protocol used to establish a direct connection between two nodes), but only if the link being monitored is the logical port which comprises multiple physical links.

## Configuring Multilink Autodiscovery in Highlight

Refer to the **Autodiscovery section on the Edit Watch Admin page** for details of how to configure autodiscovery.

Once enabled, Highlight will display and start monitoring any multilinks or bonded ports associated with the monitored interface within 30 minutes.

## Discovering switch port bonding

If you are linking multiple switch ports into a single virtual channel then Highlight can autodiscover the individual ports (members) by selecting the option 'Multilink interfaces' in the Features tab, Autodiscovery section. Once discovered Highlight will start monitoring them individually and can alert if any port members go down. Autodiscovery will only work for negotiated channels which use either Link Aggregation Control Protocol (LACP) or Port Aggregation Protocol (PAgP).

Other terms used to describe the link aggregation method include port bonding, port trunking, link bundling, Ethernet bonding, network bonding, NIC bonding, or NIC teaming.

## Discovering WAN multilinks

If the monitored bearer in Highlight is built using Cisco Multilink Point-to-Point Protocol (PPP) technology then Highlight can discover the physical links bonded by it by using the option 'Multilink interfaces' in the Features tab, Autodiscovery section. This is valuable for checking the traffic is balanced over the links and the links are reliable.

## Multilink bandwidths allocated

The set bandwidth is based on the interface name of the discovered multilink as shown here:

| Interface       | Bandwidth allocated |
| --------------- | ------------------- |
| ethernet        | 10M                 |
| fastethernet    | 100M                |
| gigabitethernet | 1000M               |
| anything else   | 2M                  |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.highlight.net/functionality/autodiscovery-multilink.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
