> 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/switch-functionality.md).

# Switch Functionality

## Overview

Highlight switch monitoring provides a detailed picture of how every switch is performing - traffic levels, health issues, and outages. Highlight is supporting an increasing list of manufacturers.

## Supported Manufacturers

Highlight currently supports the following switch manufacturers, we refer to these as **recognised switches**:

* Cisco
* Cisco Meraki
* Extreme
* HP (Procurve)
* H3C
* Juniper (including the QFX range)
* Foundry/Ruckus

For further details on specific models, please [contact us](https://help.highlight.net/getting-started/contact-us).

It may be possible to add switches from other manufacturers (or any device with 2 or more network interfaces) using **our flexible switch feature**.

## Related

* **Troubleshooting switches**
* [Details charts for switches](https://help.highlight.net/details/other-watch-types/switches)
* **Setting up switches in Highlight**


---

# 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.