> For the complete documentation index, see [llms.txt](https://docs.gxc.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gxc.io/docs/network-configuration-and-operations-guides/4g-onyx-edge-on-premises-4.x-installation-and-operations/upgrade-onyx-edge-software.md).

# Upgrade Onyx Edge Software

{% hint style="info" %}
**NOTE:** For any Onyx Edge software upgrade considerations, refer to the Onyx Edge Release Notes for the corresponding Onyx Edge release.
{% endhint %}

You can upgrade the Onyx Edge software on your Onyx Edge equipment using the Onyx Portal's Onyx Edge Upgrade Groups feature.

The Onyx Portal supports multiple Onyx Edge upgrade groups. Each Onyx Edge is associated with any one group. To upgrade the Onyx Edge software on all the Onyx Edge associated with a particular group, you must change that group’s Onyx Edge software version to the target version. The Onyx Edge software is automatically upgraded on all the Onyx Edge associated with that group.

For detailed information on managing Onyx Edge software upgrades, see *4G Onyx Portal Operations Guide > Manage Onyx Edge Software Upgrades*.


---

# 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://docs.gxc.io/docs/network-configuration-and-operations-guides/4g-onyx-edge-on-premises-4.x-installation-and-operations/upgrade-onyx-edge-software.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.