> 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/admin/admin-page/device.md).

# Device

For Controller-based devices.  SNMP devices are not editable.

The dialog header changes depending on the type of device selected. Use this panel to edit a device. Devices are autodiscovered when a controller is saved and cannot be created any other way.

{% hint style="info" %}
Highlight won't discover any watches on a device with status dormant.
{% endhint %}

### Status

This is read-only and shows Enabled or Disabled; the status of a device is set on the SD-WAN network, not within Highlight.

### Watch creation

Pending or Auto.

**Pending** — Selecting this means any uplinks, tunnels, tests and switches on a device will **not** be created and are instead visible only on the Controllers Admin page. These will not gather data so cannot change the colour of a heat tile nor send an alert.

**Auto** — This is the default option. Selecting this means any uplinks, tunnels, tests and switches on a device will be created as enabled and start gathering data. These may change the colour of a heat tile and send an alert if a measurement is below threshold.

### Name

This is read-only and shows the autodiscovered name. This name is combined with the interface name to auto-populate the description of the watches on this device.

### Description

This is optional and can contain a maximum of 100 characters.

### Reference

This is optional and can contain a maximum of 50 characters. A reference set on a device is inherited by child uplinks and tunnels unless a different reference has been set on a child uplink or tunnel. See the Inherited reference section below for more details.

### Type

This is read-only and shows the type.

Supported types:

* Cisco Meraki
* Cisco Thousand Eyes
* Cisco Catalyst
* Fortinet
* Extreme Networks
* ICMP Polling

### Discovered

This is read-only and shows the date of autodiscovery of the device.

### Controller

This is read-only and shows the controller for this device — click to open the controller. If you do not have permission to view the controller you see the text: "You do not have access to this controller."

### Save

Use to save any changes.

{% hint style="info" %}
Only description and reference can be changed.
{% endhint %}

### Delete

Use to manually remove the device from Highlight along with any previously autodiscovered watches and the parent location (if it was autodiscovered and is now empty). Any that still exist on the external network will be rediscovered.

If a device has been deleted on the external network, a red warning bar is shown reading "This device no longer exists. Scheduled for deletion." The device can be manually deleted in Highlight if needed. Alternatively, it will be deleted from Highlight after the retention period has passed.

### Switch devices

Switch devices include an additional **Features** tab, with a **Switch Port Detail** option — check it to enable additional information on a per-device basis, or uncheck to remove it.


---

# 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/admin/admin-page/device.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.