> 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/release-notes/onyx-release-notes/onyx-4.1.0-release-notes.md).

# Onyx 4.1.0 Release Notes

## Release Information <a href="#release-information" id="release-information"></a>

This Release Notes provides information about the 4G and 5G Onyx 4.1.0 release.

### Component Compatibility Information <a href="#component-compatibility-information" id="component-compatibility-information"></a>

This release has been verified to be compatible with the following component software versions.

<p align="center"><strong>4G Component Software Version Compatibility</strong></p>

| Component                                                                                                     | Release        |
| ------------------------------------------------------------------------------------------------------------- | -------------- |
| Onyx Portal                                                                                                   | 4.1.0          |
| Onyx Edge                                                                                                     | 4.1.0          |
| Mesh Node                                                                                                     | 3.1.0          |
| <p>G100 Indoor Access Point</p><p></p><p>G101 Outdoor Access Point</p><p></p><p>G501 Outdoor Access Point</p> | BaiBLQ\_3.1.14 |

<p align="center"><strong>5G Component Software Version Compatibility</strong></p>

| Component                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | Release                                            |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- |
| Onyx Portal                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      | 4.1.0                                              |
| Onyx Edge                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 4.1.0                                              |
| Onyx FHM                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | 2.0.0                                              |
| Mesh Node                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | 4.1.0                                              |
| <p>G105-n48F Indoor Access Point</p><p></p><p>G105-n48P Indoor Access Point</p><p></p><p>G105-n77 Indoor Access Point</p><p></p><p>G105-n78F Indoor Access Point</p><p></p><p>G105-n78P Indoor Access Point</p><p></p><p>G227 Indoor Access Point</p><p></p><p>G228 Outdoor Access Point</p><p></p><p>G244 Outdoor Access Point</p><p></p><p>G505-n48P Outdoor Access Point</p><p></p><p>G506-n77 Outdoor Access Point</p><p></p><p>G506-n78 Outdoor Access Point</p><p></p><p>G509-n79 Outdoor Access Point</p> | <p>For details, contact GXC Technical Support.<br> |

<br>
</p> |

## New Features, Enhancements, & Behavior Changes

This section describes new features, enhancements, and behavior changes introduced in this release.

### Onyx Portal Changes

#### On-Premises Onyx Portal Deployment

This change is applicable to both 4G and 5G networks.

This release introduces a fully self-contained, on-premises deployment of the Onyx Portal, giving you complete control over your management stack without relying on cloud infrastructure. This release is purpose-built for organizations that require local data residency, air-gapped (no-Internet) environments, or a reduced external dependency footprint.

* **Preinstalled and ready to run** — Each on-premises server ships with the on-premises Onyx Portal already installed and running. If a server ever needs to be replaced, GXC can help reinstall it — on the same or a different server — using your existing configuration.
* **Locally hosted** — Onyx Portal now runs directly within the on-premises Kubernetes cluster, with unified single-ingress routing for simplified network access.
* **Single-server deployment** — The on-premises Onyx Portal can be installed and run on a single on-premises server using a lightweight Kubernetes cluster — no cloud connectivity is required.
* **Air-gapped operation and upgrades** — Once installed, the on-premises Onyx Portal runs and upgrades entirely without Internet access; all required software, including updated Onyx Portal images, is bundled into a single upgrade package.
* **Runs on standard hardware** — Minimum server specs: 8 CPU cores, 16 GB RAM, 200 GB disk. No proprietary or vendor-specific hardware is required.
* **Health monitoring** — Built-in health checks continuously monitor the host machine and Kubernetes cluster.

**Networking and Infrastructure**

* **Flexible network interface support** — Single or dual interface configurations are supported to accommodate diverse network topologies.
* **Static IP availability** — The on-premises server maintains a consistent static IP for reliable management access.
* **Local package repositories** — Built-in local repositories enable connected Onyx Edge provisioning without Internet connectivity.
* **Portal CA certificate** — Ability to download the Onyx Portal root CA certificate, simplifying trust-chain setup for accessing the Onyx Portal and setting up Onyx Edge.

#### Alerts Sorting

This change is applicable to both 4G and 5G networks.

Alerts and Alert Rules can now be sorted alphabetically by name and severity level, making it faster to locate and prioritize alerts without manually scanning through the list. (**Alerts** > **Active Alerts** tab; **Cleared Alerts** tab; **Alert Rules** tab.)

<div data-with-frame="true"><figure><img src="https://1505800311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNOfVqlMwBhjhuClNAQ6a%2Fuploads%2FC6IS5mlqx7MX0clTqxGB%2Fimage.png?alt=media&amp;token=301d5b64-211b-49ef-899e-8b7a393cca8e" alt=""><figcaption></figcaption></figure></div>

#### Subscriber Analytics Radio Resource Usage Graphs

This change is applicable only to 5G networks.

The Subscriber Analytics page now includes two new radio resource usage graphs: UL PRB Usage and DL PRB Usage (**Subscribers** > subscriber details page > **Analytics** tab > **Plots** tab). These graphs display real-time and historical uplink and downlink Physical Resource Block (PRB) usage for the selected subscriber, providing deeper visibility into per-subscriber radio resource utilization.

* **DL PRB Usage** <br>

  <div data-with-frame="true"><figure><img src="https://1505800311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNOfVqlMwBhjhuClNAQ6a%2Fuploads%2FJVObC1LuHeQ6bVCpOVM7%2Fimage.png?alt=media&amp;token=2a6bc862-f885-4116-86a9-e81d49f213d6" alt="" width="483"><figcaption></figcaption></figure></div>

  \
  Displays the selected subscriber's downlink PRB usage over time as either a percentage (%) of available PRBs or the number (#) of PRBs allocated. PRBs are the units of radio spectrum the serving cell allocates for downlink data transmission. Higher values indicate greater downlink resource utilization, typically due to increased data reception, while sustained high utilization may indicate heavy traffic or increased demand for radio resources.
* **UL PRB Usage**<br>

  <div data-with-frame="true"><figure><img src="https://1505800311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNOfVqlMwBhjhuClNAQ6a%2Fuploads%2FXV9WtWCz7pbjnZroTe7V%2Fimage.png?alt=media&amp;token=a4428ed2-5d7c-4515-8404-1f7263271314" alt="" width="482"><figcaption></figcaption></figure></div>

  \
  Displays the selected subscriber's uplink PRB usage over time as either a percentage (%) of available PRBs or the number (#) of PRBs allocated. PRBs are the units of radio spectrum the serving cell allocates for uplink data transmission. Higher values indicate greater uplink resource utilization, typically due to increased data transmission, while consistently high utilization may indicate heavy traffic or radio resource contention.

#### Subscriber Page Performance Improvements

This change is applicable to both 4G and 5G networks.

Page load performance has been improved on pages that display subscriber information, including the Subscriber Overview page, Network Dashboard, and Equipment pages. Subscriber data is now retrieved through a single, optimized summary request instead of multiple full-dataset queries, reducing load times for networks with large subscriber counts. This is a performance improvement only — subscriber grouping, sorting, and display behavior are unchanged.

#### Renamed Network-Level Parameter and Values

This change is applicable to both 4G and 5G networks.

In the Network details page, the following parameter label and values have been renamed to more accurately and consistently reflect the function across 4G and 5G networks. This is a display-only change with no impact on underlying behavior. (**Network** > network details page > **Core** section.)

<div data-with-frame="true"><figure><img src="https://1505800311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNOfVqlMwBhjhuClNAQ6a%2Fuploads%2Fyy8ybO4BIkmnPYFtWunA%2Fimage.png?alt=media&amp;token=7526b632-a4e6-4220-a5f7-474733eb4c85" alt="" width="402"><figcaption></figcaption></figure></div>

<table><thead><tr><th width="149"></th><th>Previous Label/Value</th><th>Current Label/Value</th></tr></thead><tbody><tr><td>Parameter</td><td><strong>IP Allocation Mode</strong></td><td><strong>UE Exposure Mode</strong></td></tr><tr><td>Values</td><td>4G: <strong>LOCAL_POOL</strong><br>5G: <strong>NAT</strong></td><td><strong>NAT</strong></td></tr><tr><td></td><td>4G: <strong>DHCP_BROADCAST</strong><br>5G: <strong>VLAN</strong></td><td><strong>Direct on APN-VLAN</strong></td></tr></tbody></table>

Value mapping:

* **NAT** — UE traffic is network-address-translated
* **Direct on APN-VLAN** — UE traffic is exposed directly on the configured APN VLAN

### Core Network Changes

#### 5G Mesh Node GM03 Support

This change is applicable only to 5G networks.

{% hint style="info" %}
**NOTE**: The Mesh Node GM03 is available only for early adopter trials in this release. For more information, contact GXC Technical Support.
{% endhint %}

This release introduces Mesh Node GM03, enabling mesh networking capabilities for 5G deployments. Mesh nodes extend network coverage by creating a wireless backhaul topology, allowing operators to expand 5G connectivity to areas where traditional wired backhaul is impractical.

5G APs can now operate as Mesh APs, serving as gateway nodes for mesh node backhaul, including support for the new G228 low-power outdoor and G244 high-power outdoor APs.

Onyx Portal has been updated with full management support for Mesh Nodes and Mesh APs in 5G networks, including configuration, status monitoring, alerting, and provisioning workflows.

Operators can lock a Mesh Node UE/subscriber to a specific cell in the 5G network, providing deterministic connectivity and preventing unnecessary handovers — consistent with existing cell-lock functionality available in 4G Mesh deployments.

#### Faster Downlink Connectivity in Multi-Onyx Edge Networks

This change is applicable to both 4G and 5G networks.

In multi-Onyx Edge deployments, when a subscriber device moves from one Onyx Edge to another while retaining the same IP address, the network now broadcasts a gratuitous ARP announcement on every new attach, associating the subscriber's IP address with the new Onyx Edge's MAC address. This immediately updates the upstream router's ARP table, so downlink traffic is redirected to the correct Onyx Edge right away — significantly reducing the time it takes for downlink traffic to resume, rather than waiting for the router's outdated ARP entry to expire on its own.

#### Improved Routing Compatibility for Upstream Hosts

This change is applicable to both 4G and 5G networks.

When upstream hosts on the network send ARP requests for a subscriber's IP address, the network now replies with that subscriber's own unique MAC address, rather than a single shared MAC address used for every subscriber. This is particularly relevant for networks using "Direct on APN-VLAN" mode, where upstream hosts communicate directly with subscriber IP addresses — some applications and network management tools expect a distinct MAC address per device, and previously couldn't distinguish between subscribers because they all appeared to share the same one.

#### Improved Host Connectivity in Segmented Networks

This change is applicable only to 4G networks.

Host reachability in VLAN deployments has been improved. Previously, the system relied on receiving an ICMP redirect from the default router to learn a peer host's MAC address, and sent traffic to the default router's MAC address until that happened. In deployments where traffic is always initiated from the host side, this redirect never occurs — meaning the host was never reachable, not just intermittently. The system now proactively sends an ARP request to discover the host's MAC address directly, instead of waiting on the redirect, resolving this connectivity gap.

#### Enhanced Radio Node State Management

This change is applicable only to 5G networks.

Per-radio-node state tracking now includes a persistent mapping between each subscriber's radio connection and their subscriber identity (IMSI). This allows events raised for failed or short-lived connections — including registration failures that occur before a subscriber's session is fully established — to be correctly attributed to the affected subscriber in the Onyx Portal, rather than appearing as untraceable events.

#### Improved Per-Subscriber Tracking Reliability

This change is applicable only to 5G networks.

Reliability of per-subscriber tracking at the radio node level has been improved. Subscriber connection context is now established as soon as a connection begins, rather than sometimes being registered later — improving tracking consistency from the start of the connection. This also improves session continuity during handovers, ensuring the subscriber's connection identifier is correctly maintained as the subscriber moves between cells.

#### Enhanced Core Network Logging

This change is applicable to both 4G and 5G networks.

Logging across 4G and 5G core network components has been improved for better traceability and troubleshooting. Log entries now include consistent subscriber identifiers where applicable, making it easier to trace signaling events for individual users. Format identifiers have also been standardized across log messages for more accurate and readable output.

These improvements give network operators clearer, more consistent logs when diagnosing signaling issues — reducing the time needed to isolate and resolve connectivity or handover problems during operational monitoring.

#### Support for T3502 Timer in Registration Accept/Reject Messages

This change is applicable only to 4G networks.

The core network now supports the T3502 timer Information Element (IE) in Registration Accept and Registration Reject messages, specifying how long a subscriber device should wait before retrying registration.

#### Proactive Alert for Stalled Device Connections

This change is applicable to both 4G and 5G networks.

A new predefined alert has been added to detect when the core network stops responding to inbound device connection attempts — for example, due to an unresponsive core process — before it results in a customer-reported outage. (**Alerts** > **Alert Rules** tab.)

<table><thead><tr><th>Type</th><th>Module</th><th>Name</th><th width="106">Severity</th><th>Description</th></tr></thead><tbody><tr><td>Onyx Edge (Core)</td><td>Control Plane</td><td><strong>SCTP Outbound Stalled</strong></td><td> Major</td><td>Triggers when SCTP inbound chunks are increasing but outbound chunks are flat for the last 15 mins, indicating the core may not be responding to signaling messages.</td></tr></tbody></table>

### RAN Changes

#### Automated Frequency Change Application via Recurring Reboot Schedule

This change is applicable only to 4G networks.

Administrators can now configure a recurring reboot schedule for 4G APs so that pending frequency changes from Neighbor Management updates are applied automatically at the scheduled time, rather than requiring administrators to manually schedule a reboot to take effect. This reduces the operational overhead of applying SAS-triggered or manually configured frequency changes across a large number of APs. (**Equipment** > **Onyx Edge** tab > Onyx Edge details page > **Actions** > **Reboot Neighbor Updated APs**.)

<div data-with-frame="true"><figure><img src="https://1505800311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNOfVqlMwBhjhuClNAQ6a%2Fuploads%2FAYUv8L4Wz8zyYUBuRvxf%2Fimage.png?alt=media&amp;token=7106d11f-4335-4844-9b11-910c6cfb0078" alt="" width="563"><figcaption></figcaption></figure></div>

#### Expanded 5G AP Support

This change is applicable only to 5G networks.

The Onyx system now supports the following new 5G AP models:

* **G227** — Indoor, Low Power
* **G228** — Outdoor, Low Power
* **G244** — Outdoor, High Power
* **G509-n79** — Outdoor, High Power

#### 5G Onyx Edge Support for gNBs

This change is applicable only to 5G networks.

This release adds support for operating Onyx Edge with gNBs, beginning with the following models. Unlike fiber-connected APs, these gNBs use Ethernet-based backhaul, adding deployment flexibility for indoor and outdoor private 5G scenarios alongside your existing O-RAN-based APs.

* **G227** — Indoor, Low Power
* **G228** — Outdoor, Low Power
* **G244** — Outdoor, High Power

#### AP & FHM Management Improvements

This change is applicable only to 5G networks.

This release delivers the following improvements to AP and FHM management.

* Invalid Spectrum Grant Power Handling — The system now gracefully handles scenarios where a spectrum grant results in a power level below the AP's supported minimum. In which case, the AP's transmit is automatically disabled and the "Insufficient SAS Power" Onyx Portal alert is triggered, preventing the AP from operating at an unsupported power level.

  <table><thead><tr><th>Type</th><th>Module</th><th>Name</th><th width="106">Severity</th><th>Description</th></tr></thead><tbody><tr><td>Access Point</td><td>CU Plane</td><td><strong>Insufficient SAS Power</strong></td><td> Major</td><td>Triggers when SAS granted power is below the AP hardware minimum; transmission has been disabled</td></tr></tbody></table>

* Extended Frequency Range for G506-n78 on Band n78 — Frequency support for G506-n78 on Band n78 has been extended, enabling deployments at higher center frequencies. The previous Onyx Portal-side restriction has been removed to reflect the full range supported by the AP firmware.

#### Cell Health Alerts

This change is applicable only to 5G networks.

The following new predefined alerts have been added to monitor 5G NR cell health, enabling operators to detect and respond to degraded radio conditions before they impact end-user experience. (**Alerts** > **Alert Rules** tab.)

* High Error Rate Alerts — Trigger when the air interface error rate remains elevated for a sustained period, with separate alerts for uplink and downlink directions.

  | Type           | Module     | Alert Name            | Severity | Description                                                     |
  | -------------- | ---------- | --------------------- | -------- | --------------------------------------------------------------- |
  | Onyx Edge (NR) | User Plane | **Cell High DL BLER** | Warning  | Alerts when DL BLER > 50% for the cell for at least 15 minutes. |
  | Onyx Edge (NR) | User Plane | **Cell High UL BLER** | Warning  | Alerts when UL BLER > 50% for the cell for at least 15 minutes. |

* Timing Issue Alerts — Trigger when excessive early or late packet timing errors are detected over a sustained period.

  <table><thead><tr><th>Type</th><th>Module</th><th>Alert Name</th><th width="105">Severity</th><th>Description</th></tr></thead><tbody><tr><td>Onyx Edge (NR)</td><td>User Plane</td><td><strong>Early eCPRI Packets</strong></td><td>Warning</td><td>Alerts when more than 50% of eCPRI packets are early in the last 15 minutes.</td></tr><tr><td>Onyx Edge (NR)</td><td>User Plane</td><td><strong>Late eCPRI Packets</strong></td><td>Warning</td><td>Alerts when more than 50% of eCPRI packets are late in the last 15 minutes.</td></tr></tbody></table>

* Fronthaul Connectivity Alert — Detects loss of bidirectional connectivity between the baseband unit and radio unit when the transmit path is active but the receive path is down.

  <table><thead><tr><th>Type</th><th>Module</th><th>Alert Name</th><th width="105">Severity</th><th>Description</th></tr></thead><tbody><tr><td>Onyx Edge (NR)</td><td>User Plane</td><td><strong>eCPRI Rx Down</strong></td><td>Warning</td><td>Alerts when no eCPRI RX packets are received for 15 minutes even with Tx enabled.</td></tr></tbody></table>

#### RAN Handover Enhancements

This change is applicable only to 5G networks.

This release improves handover behavior for RAN deployments.

{% hint style="info" %}
**NOTES**:

* In this release, handovers are supported only either between gNBs (G227, G228, G244) or between ORAN APs, and not across the two types.

* A maximum of four explicit neighbors can be configured per cell.

* These improvements are available only in conjunction with Onyx Edge running 4.1.0 and later releases.&#x20;
  {% endhint %}

* **Explicit Neighbors** — Neighbors of a cell can be explicitly chosen.

* **A1/A2-Based A5 Configuration** — RAN previously configured the A5 handover event unconditionally for every UE. The network now uses A1 and A2 measurement events to determine when A5 configuration is actually needed (in cell edge cases), reducing unnecessary measurement signaling and improving radio resource utilization.

* **(5G) Configurable Handover Thresholds** — Handover thresholds for 5G RAN deployments are now configurable under Onyx Edge settings in the Onyx Portal, rather than being fixed. (**Equipment** > **Onyx Edge** tab > Onyx Edge details page > edit Onyx Edge > **RAN** tab > edit Cell > **Edit Cell** dialog box > **Handover** tab > **Show Advanced Configuration**.)<br>

  <div data-with-frame="true"><figure><img src="https://1505800311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNOfVqlMwBhjhuClNAQ6a%2Fuploads%2FY4YFCCRNOx5mk6yp3ofw%2Fimage.png?alt=media&amp;token=f226e907-a1f5-408d-9f8b-259a550bfd67" alt="" width="563"><figcaption></figcaption></figure></div>

  \
  The Onyx Edge details includes RSRP report levels in dBm using standard A-event labels. (**Equipment** > **Onyx Edge** tab > Onyx Edge details page > **Handover** tab.)<br>

  <div data-with-frame="true"><figure><img src="https://1505800311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNOfVqlMwBhjhuClNAQ6a%2Fuploads%2FeOnCzJ91VgUZev8YWSue%2Fimage.png?alt=media&amp;token=9d9bd96b-2c20-4110-b68e-7734146c65c8" alt=""><figcaption></figcaption></figure></div>

## **Resolved Issues**

The following issues reported in previous releases were resolved in this release.

* **Intermittent M-Plane Connection Failure for Call-Home Radio Units** — (5G only) During cell delete-and-add operations or simultaneous addition of two cells, the RU Manager may fail to establish the M-Plane connection to one of the call-home RUs, leaving it unconfigured until a subsequent retry or manual intervention. This issue is specific to the G505/G506 RU models.
* **Critical Services Fail to Initialize After Simultaneous Reboot of Both Onyx Edges in an Onyx Edge Pool** — In Onyx Edge pools containing two Onyx Edge AGWs, simultaneously rebooting both units could cause critical services to fail to start, because the ports they require were allocated to other processes during the reboot.
* **Large Packets With DF Bit Not Set Are Not Processed** — Large packets with the Don't Fragment (DF) bit not set were not processed correctly in Multi-APN-VLAN (Non-NAT) mode.

## Open Issues <a href="#open-issues" id="open-issues"></a>

{% hint style="info" %}
**NOTE**: Open issues reported in previous releases, unless subsequently reported as resolved, may exist in this release.
{% endhint %}

There are no new open issues reported in this release.


---

# 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://docs.gxc.io/release-notes/onyx-release-notes/onyx-4.1.0-release-notes.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.