> 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/getting-started/release-notes/24.9-september-2024.md).

# 24.9 - September 2024

Release Notes 24.9 for September 2024

### Summary

In **24.9** we add support for Meraki connectivity tests on uplinks.

### Cisco Meraki connectivity tests on uplinks - Beta

<figure><img src="https://25768351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68Wb63XzG9guH74bkPEb%2Fuploads%2F5QvPiLiNodvE3CSSAZvF%2FCiscoMerakiLogo.png?alt=media&amp;token=56504f02-7c28-4317-b53a-715d24833b58" alt=""><figcaption></figcaption></figure>

Released in Beta, from 24.9 you can track the performance of internet connections on Meraki uplinks. Like other performance tests in Highlight, these are shown in the grid, as a badge on the watch status card and on the uplink details page.

<figure><img src="https://25768351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68Wb63XzG9guH74bkPEb%2Fuploads%2Fu3G3IbcCda4yu4WIS2XO%2FMerakiUplinkWatchStatusCardPerfTest.png?alt=media&amp;token=d8030faf-3944-474f-8da1-e357c19e7fc0" alt=""><figcaption><p>Watch status card: Uplink with red Performance badge</p></figcaption></figure>

Highlight enables you to set thresholds on the response time for connectivity tests and run daily, weekly or monthly reports on response time and packet loss.

<figure><img src="https://25768351-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68Wb63XzG9guH74bkPEb%2Fuploads%2FnpyZnUP5Ci5nWDmeK1is%2FMerakiUplinkTestChart.png?alt=media&amp;token=24768019-907a-4359-a104-510261b9f41a" alt=""><figcaption><p>Details page: Uplink connectivity test chart showing source and target plus metrics in the tooltip</p></figcaption></figure>

Find out more about [adding uplink connectivity tests to your Cisco Meraki controller](https://support.highlight.net/help/admin/sdwan_controllers#create_edit_controller_cisco_meraki) or [contact us](https://help.highlight.net/getting-started/contact-us.md) to set this up.

### Bug fixes

* **Edit watch:** It's now possible to disable previously enabled switch port monitoring.
* **Traffic load chart:** Saved settings now work as expected for Percent vs Actual.

### Service description

The [Highlight Service Description document](https://support.highlight.net/help/getting_started/HighlightServiceDescription.pdf) concisely describes how Highlight works and its key features. It has been updated for 24.9 and is available on the Help & Support Centre.

### Browser compatibility

All Highlight releases are tested on the current version of:

* ![Chrome](https://support.highlight.net/help/images/browser_chrome.png)

  #### Chrome
* ![Edge](https://support.highlight.net/help/images/browser_edge.png)

  #### Edge
* ![Firefox](https://support.highlight.net/help/images/browser_ff.png)

  #### Firefox

Find out more about [Highlight supported browsers](https://help.highlight.net/getting-started/useful-information/browsers-supported.md).

### Get in touch

More details on all of Highlight’s features are available on the Help & Support Centre or [contact us](https://help.highlight.net/getting-started/contact-us.md) for assistance.


---

# 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/getting-started/release-notes/24.9-september-2024.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.
