> 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.0.1-release-notes.md). # Onyx 4.0.1 Release Notes ## Release Information This release note provides information about the 4G and 5G Onyx 4.0.1 release. ### Component Compatibility Information This release has been verified to be compatible with the following component software versions.

4G Component Software Version Compatibility

| Component | Release | | ------------------------------------------------------------------------------------------------------ | -------------- | | Onyx Portal | 4.0.1 | | Onyx Edge | 4.0.1 | | Mesh Node | 3.1.0 | |

G100 Indoor Access Point


​G101 Outdoor Access Point

​G501 Outdoor Access Point

| BaiBLQ\_3.1.14 |

5G Component Software Version Compatibility

| Component | Release | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- | | Onyx Portal | 4.0.1 | | Onyx Edge | 4.0.1 | | Onyx FHM | 2.0.7 | |

G105-n48F Indoor Access Point

G105-n48P Indoor Access Point

G105-n77 Indoor Access Point

G105-n78F Indoor Access Point

G105-n78P Indoor Access Point

G505-n48P Outdoor Access Point

G505-n78P Outdoor Access Point

G506-n77 Outdoor Access Point

| For details, contact GXC Technical Support. | ## New Features, Enhancements, and Behavior Changes This section describes new features, enhancements, and behavior changes introduced in this release. ### 5G Core-Only High Availability Support This change is applicable only to 5G networks. This release introduces High Availability (HA) support for standalone 5G Core-only deployments, improving network resilience and service continuity within Onyx Edge pools. * Onyx Edge pooling provides HA by grouping multiple Onyx Edge nodes into a pool. All Onyx Edge nodes operate in active-active mode with equal capacity. If an Onyx Edge node fails, UE registered on that node are automatically transferred to other Onyx Edge in the pool with minimal service disruption. * Onyx Portal Support for 5G Core-Only HA — The Onyx Portal has been updated to support 5G Core-Only HA configuration and status display, enabling operators to monitor and manage HA deployments. * HA Peer Down Alert — A new alert notifies operators when the peer node in a 5G Core-only HA deployment becomes unreachable. ### Neighbor Management Updates for AP in 4G This change is applicable only to 4G networks. This release introduces neighbor management enhancements for 4G AP deployments, giving users greater control over how configuration changes are propagated and applied across APs. * **Reboot on Neighbor Update** Configuration — A new network-wide setting, **Reboot on Neighbor Update**, gives users control over how neighbor configuration changes are applied to APs.

NOTE: In existing networks, the Reboot on Neighbor Update parameter is enabled by default to maintain pre-4.0.1 behavior. In networks created in release 4.0.1 or later, it is disabled by default.

* When Off: Saving an AP with neighbor changes will not take effect until the AP is manually rebooted. For frequency changes (on a non-SAS AP or a SAS AP's preference parameters), neighboring APs need to be rebooted to apply the changes. In both cases, a warning message indicating the APs need to be rebooted manually is displayed. The reboot can be triggered immediately or scheduled for later in the Onyx Portal interface. * When On: Saving an AP with neighbor changes will result in the AP rebooting automatically to apply the changes. For frequency changes (on a non-SAS AP or a SAS AP's preference parameters), the AP and its neighboring APs will be rebooted automatically to apply the changes. In both cases, a warning message indicating the APs will be automatically rebooted is displayed. * **Config/FSM State** parameter — On the AP details page, the **Config/FSM State** parameter now includes two additional states indicating whether an AP reboot is pending for neighbor updates: * **PENDING\_REBOOT\_WITH\_SCHEDULE** — Indicates reboot is pending and is scheduled for a specified time. The scheduled time is shown in the **Reboot Schedule for Neighbor Update** parameter. * **PENDING\_REBOOT\_WITHOUT\_SCHEDULE** — Indicates reboot is pending but not yet scheduled. User action is required to schedule the reboot before neighbor changes will take effect. * In the AP summary and AP details pages, hovering over the Service Status icon now displays the Neighbor Update Status — **IN\_SYNC** or **NOT\_IN\_SYNC**. * Scheduled Reboot Commands — From the **Equipment** > **Onyx Edge** tab > Onyx Edge details page > **Actions** menu, users can now use the **Reboot Neighbor Updated AP** command to schedule reboots for APs with pending neighbor changes: * Reboot all APs with reboot pending at a chosen time, including immediately. * Reboot a specific AP by serial number, if it has a reboot pending, at a chosen time including immediately. #### Known Limitations * Scheduled Reboot Time Validation — The "Reboot Neighbor Updated APs" scheduling popup screen currently allows manual entry of past time values without validation. This is planned to be addressed in an upcoming release. ### Onyx Portal Improvements This release introduces Onyx Portal enhancements across the Onyx Edge and subscriber management workflows. The changes described below cover UI refinements, default value changes, and new bulk-action capabilities for subscriber group management and tenant administration. * Bulk-assign subscribers to non-default groups — (4G & 5G) Subscribers can now be assigned directly to a non-default subscriber group when moving them from GXC Root to a network, eliminating the need to first place them in the default group and then move them individually. * Bulk-move subscribers across subscriber groups — (4G & 5G) A new bulk-selection capability lets you move multiple subscribers from one or more source groups to a target group in a single operation, significantly reducing manual effort. * Show Graphs / Hide Graphs toggle on Onyx Edge summary page — (4G & 5G) The **Equipment** > **Onyx Edge** page now includes a collapsible graphs panel that defaults to collapsed to improve page performance. Users can expand it to view the performance charts — **UE Throughput**, **Onyx Edge Connected with Onyx Portal**, and **UE Attach Status**. * Timing Source default value and layout — (5G only) In the Add/Edit Onyx Edge pages, the **Timing Source** field now defaults to **FREE RUNNING** and has been repositioned for better visibility. * Cell form improvements — (5G only) In the Add/Edit Cell screens, the "**PSS**" field has been renamed to "**PSS (for PCI)**" to clarify its role. ### Fronthaul Multiplexer Release 2.0.7 Fronthaul Multiplexer (FHM) Release 2.0.7 is available in conjunction with this Onyx 5G release. It does not introduce any new features or enhancements and is provided to maintain compatibility with other components of the release. ## Resolved Issues There are no previously reported open issues resolved in this release. ## Open Issues {% hint style="info" %} **NOTE**: Open issues reported in previous releases, unless subsequently reported as \ resolved, may exist in this release. {% endhint %} The following new open issues are reported in this release. 1. **DU log rotation causing end-user data transfer glitches** — The Distributed Unit (DU) log verbosity setting is higher than optimal, causing logs to rotate every few hours. During each rotation, the log compression process competes for CPU resources on the same cores dedicated to real-time DU processing, resulting in perceptible momentary disruptions or degraded throughput for end users during rotation events. This issue will be addressed in an upcoming release. 2. **FHM SyncE status incorrectly reported as "Not Locked" in Onyx Portal —** The Fronthaul Multiplexer (FHM) SyncE synchronization status is incorrectly displayed as "Not Locked" in the Onyx Portal, even when the FHM's SyncE and DPLL clocks are in a valid locked state. This is caused by the FHM hardware not accurately reporting its SyncE lock state to the gateway, resulting in a mismatch between the actual clock state and what is shown in the Onyx Portal dashboard. Network operators may observe false SyncE synchronization alarms or status indicators for FHM equipment, potentially leading to unnecessary investigation of timing and synchronization that is functioning correctly. This issue will be addressed in an upcoming 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.0.1-release-notes.md?ask=&goal= ``` `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.