> 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/troubleshooting/switches.md).

# Switches

## Overview

This page explains symptoms experienced with Switch monitoring.

## Symptom 1. Details page showing "Highlight has no data"

After clicking the Switch card in the watch status panel, if the Details page shows "Highlight has no data for this period" for Port Summary and Critical Ports show empty charts, this is likely to be because Highlight does not currently support switches with greater than 255 ports.

#### Action

There is no current solution or workaround. However please [contact us](/getting-started/contact-us.md) to let us know you have experienced this symptom.

## Symptom 2. Switch port monitoring not available

If the entry for Switch port monitoring is greyed out in the Edit Watch: Features tab, try going to the Main tab and techtest. If the techtest reports "Identified Switch Device" return to the Features tab to Enable Switch port monitoring.

Note: you have to save and re-open the Features tab to be able to select Critical ports

## Symptom 3. Juniper switch port zero not shown

The ports on any switch in Highlight are labelled in the standard way, starting at 1.

Juniper switches start from port zero. Highlight discovers all ports on a Juniper switch but labels each one number higher than Juniper does.

*Example Technical Information dialog for Juniper: port 1 is, in fact, port 0 and port 24 is actually port 23*

## Symptom 4. Flexible switch error on details page

If you see this error on the details page for a flexible switch which previously worked, possible reasons for this include the following:

1. A flexible switch has been created on the same device in 2 or more locations
2. A previously created interface on a flexible switch has been removed

#### Action

[Contact us](/getting-started/contact-us.md) to discuss alternative implementations


---

# 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/troubleshooting/switches.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.