> 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-vlan.md).

# Autodiscovery - VLAN

## Overview

Highlight can discover VLANs (sub-interfaces) on bearers monitored using a physical interface. Each discovered VLAN will have its own watch status card and details page.

## Configuring VLAN Autodiscovery in Highlight

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

After validation, Highlight then waits 15 minutes, so that any new circuits have time to start and 'claim' VLANs.

For a VLAN to be discovered it must be a sub-interface to the bearer interface being monitored - so for example a LinkHealth report which is monitoring FastEthernet0/0 will ONLY find VLANs which take the form FastEthernet0/0.x

The VLAN itself must be one of a predefined list of VLAN types, as follows:

| ifType | Description |
| ------ | ----------- |
| 135    | l2vlan      |
| 136    | l3ipvlan    |
| 137    | l3ipxvlan   |

If these criteria are met, the VLAN will be 'recognised' and Highlight will start monitoring it.

Note that errors and congestion are not normally available for subinterfaces like VLANs, so are not collected/reported.


---

# 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-vlan.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.
