# Onyx 4.0.0 Release Notes
## Release Information
This release note provides information about the 4G and 5G Onyx 4.0.0 release.
### Component Compatibility Information
This release has been verified to be compatible with the following component software versions.
| 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.
### Alerts and Alert Notifications
These changes are applicable to 4G and 5G networks.
* **New Predefined Alerts**:
* **"DHCP Server Failed"** — (4G & 5G) Triggered when the DHCP server responsible for assigning IP addresses to UE is unavailable. For more information, see [*DHCP Server Monitoring*](#dhcp-server-monitoring).
Type
Module
Name
Severity
Onyx Edge (Core)
Control Plane
DHCP Server Failed
Major
* **"TR-069 Session Stuck"** — (4G only) Triggered when a TR-069 session with an AP cannot complete and is stuck in an error loop. This alert enables faster detection of device configuration issues before they can cause prolonged outages.
Type
Module
Name
Severity
Access Point
Management Plane
TR-069 Session Stuck
Major
* **"SAS Connection Failure" Alert Consolidation at Domain Proxy Level** — (4G & 5G) SAS Connection Failure alerting now generates a single consolidated alert at the Domain Proxy level instead of individual alerts per AP, reducing alert noise and improving visibility in large deployments.
### Analytics
These changes are applicable to 4G and 5G networks.
* **New Performance Analytics Charts**:
* **"NGAP Dropped Connections"** — (5G only) A new "NGAP Dropped Connections" KPI chart displays the percentage/count of connections dropped due to radio/RAN issues versus normal releases (UE-initiated, network-initiated, idle timeout).
* **"Paging Success"** — (4G & 5G) A new "Paging Success" KPI chart displays the percentage/count of paging success rates, indicating potential RF coverage issues or coverage gaps when paging response rates are low.
* **"RACH Attempts"** — (5G only) A new "RACH Attempts" KPI chart displays the number of RACH preambles detected by the cell, enabling users to assess RACH load and potential contention, and quickly correlate random access attempts with RRC connections for clearer insight into access performance.
* **"RRC Connection Establishments"** — (5G only) (Previously "RRC Success Percentage") This chart has been renamed and significantly enhanced. The chart now displays RRC connection volume and success rate in a single grouped bar chart, with two data series: Successful (green) and Attempted (blue), plotted as raw connection counts over time.
* **Auto-Selection of Single-Choice Hierarchy Levels** — (4G & 5G) When only one option exists at a hierarchy level (e.g., a single network, venue, or Onyx Edge), the Onyx Portal now selects it automatically, so users with simple network topologies reach their target AP or cell in fewer clicks.
* **Context-Aware Analytics Display for Core-Only Deployments** — (5G only) For Onyx Edge Core-only deployments, RAN and mobility KPIs are now hidden, providing a cleaner, more contextually relevant analytics view.
* **AP Names in Performance Charts** — (4G & 5G) Gateway AP names are now displayed in performance charts instead of numeric identifiers, making it easier to identify and troubleshoot AP behavior without cross-referencing IDs.
### Events
These changes are applicable to 4G and 5G networks.
This release delivers a significant expansion of 5G event coverage across the RAN and Core, improving observability, reducing troubleshooting time, and bringing 5G event parity with existing LTE capabilities.
* **5G RU and FHM Events and Alerts** — (5G only) The 5G RU and FHM equipment details page now **includes** a dedicated Events & Alerts tab. Users can view per-equipment alerts and events in one place, correlating connectivity, configuration, and fault events without switching contexts. (**Equipment** > **FHM** tab > FHM details page > **Events & Alerts** tab), (**Equipment** > **Access Point** tab > AP details page > **Events & Alerts** tab).
* **Configuration Changes** — AP configuration update events now include the actual parameter changes — for example, frequency or transmit power adjustments — rather than generic "config updated" notifications. Importantly, simple configuration changes no longer generate spurious disconnect or fault events alongside them.
* **Connect / Disconnect Sequencing** — When a managed RU or FHM disconnects and reconnects, you now reliably see a disconnect event followed by a reconnect event, providing an unambiguous start-to-finish record of the outage and recovery. This reduces noise and ambiguity when investigating transient link failures.
* **Unrecognized Devices** — Redundant IP fields have been removed from the device record; the IP is now reported in a single consistent location under the associated AP or FHM, making these events easier to read and filter.
* **FHM Passthrough** — Duplicate or overlapping events when FHM passthrough is enabled have been eliminated. Passthrough events are now symmetrical (enable/disable) and consistent.
* **Hyperlinks from 5G Events to Associated AP/FHM** — (5G only) Cell-ID hyperlinks for 5G events now navigate to the associated AP/FHM page.
* **5G Session Rejected Event** — (5G only) A new "session\_rejected" event captures PDU session establishment failures with detailed rejection reasons (e.g., non-subscribed DNN, max PDN limit), improving 5G troubleshooting visibility.
* **Subscriber Events** — (5G only) Subscriber events now support distinct 5G event types, enabling more precise filtering and diagnostics.
* **UE Idle Transition Reason Now Included in Events** — (4G & 5G) Subscriber events now include the reason a UE transitioned to Idle state — such as inactivity timer expiry, Radio Link Failure (RLF), paging failure, or Tracking Area Update (TAU) — making it easier to correlate state changes with specific network or subscriber behavior.
### DHCP Server Monitoring
This change is applicable to 4G and 5G networks for Onyx Edge in VLAN mode.
A new DHCP server monitoring mechanism validates DHCP server availability independently of real UE traffic, ensuring failures remain visible even when real UE are idle.
* **Onyx Portal Configuration** — Users can now configure and monitor DHCP behavior directly in the Onyx Portal, improving visibility and simplifying troubleshooting for Onyx Edge deployments.
* **Onyx Edge Add/Edit pages** – New DHCP monitoring configuration allows users to enable/disable monitoring and configure parameters per Onyx Edge. To enable DHCP server monitoring, at least one APN with a VLAN must be configured. (**Equipment** > **Onyx Edge** tab > Add/Edit Onyx Edge > **Core** tab > **DHCP Server Monitoring** section)
* **Onyx Edge Details page** – A new DHCP Server Monitoring status summary provides at-a-glance visibility into DHCP health per Onyx Edge. (**Equipment** > **Onyx Edge** tab > Onyx Edge Details page > **Overview** tab > **Core** section).
* **New Predefined Alert** — A new predefined alert, "DHCP Server Failed", raises a major alert when the DHCP server is unavailable.
### **FHM Fiber Length Configuration**
This change is applicable only to 5G networks.
FHM add/edit configuration now includes a per-RU **Fiber Length (km)** parameter, allowing users to specify the fiber length between the FHM and associated RU. The system uses these values to automatically calculate and apply RU transmit delay compensation, improving timing alignment across RUs connected via different fiber lengths.
The **Fiber Length** field accepts positive numeric values up to two decimal places (e.g., 0.25, 3.50). Changes to fiber length trigger a configuration update to the Onyx Edge, ensuring the updated compensation is applied immediately.
(**Equipment** > Add/Edit FHM page > **Selected RUs Configuration** section)
### **Force Status Sync from Onyx Edge Action Control**
This change is applicable to 4G and 5G networks.
A new **Force Status Sync from Onyx Edge** action control in the Onyx Portal allows users to manually trigger Onyx Edge state synchronization — useful when investigating stale status displays or validating a change without waiting for the next periodic sync. (**Equipment** > **Onyx Edge** tab > Onyx Edge details page > **Actions** button).
### Multi-Cell & Handover Support
These changes are applicable only to 5G networks.
This release introduces end-to-end multi-cell and handover support.
* **Multi-Cell Support**
* Up to three NR cells per DU are now supported, with each cell configured as neighbor to each other for intra-gNB handovers.
NOTE: In multi-cell deployments, measurement reports are always configured, causing UE to consume radio resources on measurement gaps reducing overall throughput.
* The gNB now starts and operates with available cells even if some RU or cells are not ready, improving robustness in real-world deployments.
* **Per-Cell Metrics & Analytics**
* Core and RAN KPIs are now reported per cell. Onyx Portal analytics can be filtered by cell, with new visualizations showing serving cell transitions per subscriber to validate handover behavior.
* **Core Network – Cell Tracking** — The serving cell for each subscriber is now updated across a broader range of uplink procedures, ensuring Onyx Portal analytics and troubleshooting tools always reflect the actual serving cell during and after handovers.
* **PCI Management** — NR Physical Cell ID (PCI) allocation is now updated with logic to avoid collisions among neighboring cells. Onyx Portal configuration aligns with this model, providing a consistent and reliable approach to PCI management in multi-cell deployments.
* **Xn Handover for 5G** — (Core only) Inter-gNB Xn handover is now supported, enabling seamless mobility between 5G cells.
### N48 AP Low-Power Warning
When a G105-N48 AP is configured below 21 dBm, the Onyx Portal now displays a warning alerting users that operating below this threshold may reduce coverage area and performance, ensuring users are informed before applying a low-power configuration.
### Speed Test Enhancements
These changes are applicable to both 4G and 5G networks.
This release delivers a comprehensive set of improvements to the Speed Test feature, enhancing reliability, performance, and the overall user experience. Users benefit from faster, more accurate results, configurable test servers, and a more intuitive interface.
* **Configurable Speed Test Servers** — The list of speed test (iPerf) servers is now fully configurable at the network level. Users can add, remove, or reorder servers per gateway instead of relying on a hardcoded default list. This ensures that if a specific server is unavailable, speed tests remain functional.
* **On-Demand Per-Gateway Refresh** — A new per-gateway refresh button allows users to trigger a speed test for a specific Onyx Edge on demand. Previously, the refresh action ran tests across all gateways simultaneously. This enables more targeted and efficient testing.
* **Automatic Result Updates** — Speed test results now update automatically after a test completes, removing the need to manually refresh the page to see updated results.
* **Cached Results on Page Load** — Upon entering the speed test page, the system now displays the most recent cached result from the gateway status instead of triggering a new speed test. This significantly reduces page load times and avoids unnecessary network load.
* **Smarter Test Throttling** — The Onyx Edge now enforces a cooldown period to prevent excessive, back-to-back speed tests. A force parameter is available for explicit user-initiated refreshes when an immediate re-test is needed.
* **Enhanced iPerf Server Retry Logic** — The speed test engine now uses an improved server rotation strategy — it tries the first port on all configured servers before moving to subsequent ports, ensuring faster fallback when a server is down. Additionally, if the uplink test succeeds on a particular server/port, the downlink test automatically uses the same connection.
* **Ping Results Reported Independently** — Ping and latency results are now reported even when iPerf throughput tests fail, ensuring users always receive partial diagnostic data rather than a completely blank result.
* **Offline Gateway Refresh Disabled** — The refresh button is now disabled for offline Onyx Edge, preventing users from initiating speed tests that cannot complete.
* **UI Status Text Improved** — The "Loading" indicator that appeared when initiating a speed test has been replaced with a clearer "Speed Test Initiated" message to better communicate system status.
### **Subscriber Analytics and Reporting**
These changes are applicable to both 4G and 5G networks.
* **New Subscriber Analytics**
* **"Serving Cell Transition" Chart** — (5G only) Subscriber Analytics has been enhanced with a new "Serving Cell Transition" chart, providing per-subscriber visibility into serving cell transition to 5G.
* "**DL RSRP**" **Chart** — (5G only) Subscriber Analytics has been enhanced with a new "**DL RSRP"** (Reference Signal Received Power) chart, providing per-subscriber visibility into radio signal quality.
* **Subscriber State Reporting** — (4G & 5G) Subscriber states have been updated to provide clearer visibility into the subscriber lifecycle. These changes are reflected across the subscriber summary, subscriber details, Onyx Portal Dashboard, and Onyx Edge and AP/RU details pages.
* **Not Yet Connected** — A new dedicated state for subscribers who have never registered on the network, making it easy to identify un-provisioned or never-online subscribers at a glance.
* **Detached (previously "Not Connected")** — Renamed to align with standard 3GPP terminology. Now exclusively represents subscribers who were once connected but have since disconnected.
* **Unknown State Removed** — Previously used for edge cases when an Onyx Edge was offline; these cases are now handled by the Detached state.
* **Updated Color Coding** — "Not Yet Connected" subscribers are shown in black, "Detached" subscribers remain grey, and "Disabled" subscribers are shown in red.
* **gNB ID / Cell ID Links to FHM/AP Detail Pages** — In the subscriber summary and subscriber details pages, the **gNB ID/Cell ID** entries now link to their corresponding FHM/AP details pages. Users can now navigate directly to the relevant FHM/AP page, improving troubleshooting and traceability workflows.
### Survey Solution Enhancements
This change is applicable to both 4G and 5G networks.
The Survey solution has been enhanced to improve survey management, visualization, and comparison workflows.
* **Data Export** — Added ability to download raw survey files from the Onyx Portal. Supports exporting survey data for external analysis and archival.
* **Survey Management** — Users can now delete surveys directly from the Onyx Portal. Users can also add survey labels and comments to annotate survey log files and coverage overlay files for easier identification and context.
* **Improved Survey Selection UX** — The survey dropdown now sorts entries by date (most recent first), making it easier to find and work with the latest surveys.
* **Combine Multiple Surveys** — Added the ability to combine two surveys into a single, consolidated survey view. Includes safeguards around performance and distance constraints when combining surveys, and support for differentiating non‑overlapping survey data in the graphs.
* **Basemap KMZ Import & Coverage Comparison** — Added support to import a KMZ basemap and overlay it with survey data. Enables visual comparison of prediction vs. actual coverage on the same map, with aligned legends/colors where possible.
* **Registered RUs Now Shown on Map** — The map view now displays RUs (APs) based on GPS, SAS or user input. AP indicators can be added manually for units not yet provisioned in the network, improving correlation between survey data and deployment.
* **Previous scan results are preserved and shown by default** — The scanner now saves results from previous runs. When a user opens the CBRS Scanner page, the last completed scan is shown by default, so users can immediately review the most recent spectrum view without having to re‑run a scan.
* **Optimized CBSD scan time** — The scan workflow has been optimized to reduce the time to complete a CBRS scan, improving responsiveness for venue operators. These improvements make it faster to validate CBRS activity and refine spectrum planning.
* **Show GXC CBSDs on the map** — The scanner map now displays GXC CBSDs directly in the UI, allowing users to see where the CBSDs are located relative to the scanned CBRS activity. This makes it easier to correlate scan results with deployed infrastructure and analyze coverage/placement.
* **Previous Scan Results Preserved and Shown by Default** — The scanner now saves results from previous runs. When a user opens the CBRS Scanner page, the last completed scan is shown by default, so users can immediately review the most recent spectrum view without having to re‑run a scan.
* **Optimized CBSD Scan Time** — The scan workflow has been optimized to reduce the time to complete a CBRS scan, improving responsiveness for venue operators. These improvements make it faster to validate CBRS activity and refine spectrum planning.
* **GXC CBSDs Shown on Map** — The scanner map now displays GXC CBSDs directly in the UI, allowing users to see where the CBSDs are located relative to the scanned CBRS activity. This makes it easier to correlate scan results with deployed infrastructure and analyze coverage/placement.
### UE IP-Pool Management for VLAN Mode
This change is applicable to both 4G and 5G networks.
The Onyx Edge in VLAN networking mode now fully supports IP pool management for UE. Users can now define and adjust IP pools in VLAN mode, enabling faster network configuration updates and better IP resource isolation across deployment scenarios.
The Onyx Portal Add/Edit Onyx Edge pages and the APN Add/Edit pages now allow configuring UE IP pools in the VLAN mode, including controls to create and edit IP blocks and monitor assigned and available IP ranges for VLAN-based UE.
#### **IP Retention Time Configuration**
An **IP Retention Time** parameter is now available in the Onyx Edge configuration for both NAT and VLAN modes allowing users to specify how long a UE's IP address is retained after the UE disconnects. This provides finer control over IP address allocation and reuse behavior.
### Onyx Edge Equipment Changes
#### **Mobile Network Gateway**
The Mobile Network Gateway (MNG), a portable, self-contained Onyx Edge (NR + Core) unit, is now available for deployments. For more information, see the *5G MNG 00X Specification Sheet*.
#### **Disk Encryption with Hardware-Backed Key Protection**
The Onyx Edge now supports Linux Unified Key Setup (LUKS) disk encryption with Trusted Platform Module (TPM) integration, enabling hardware-backed key protection and secure, automated unlocking of encrypted storage on supported platforms.
#### gnbs CLI Command for agw\_user
This change is applicable to both 4G & 5G networks.
A new CLI command, **`gnbs`**, is now available to the *agw\_user* account on Onyx Edge, enabling quick listing of connected gNBs for operational checks.
#### Local Configuration Interface for Onyx Edge NR
This change is applicable only to 5G networks.
A browser-based Local Configuration Interface (LCI) is now available for Onyx Edge NR gateways, accessible directly over HTTPS on the gateway — including in headless mode (without a connected display) or without internet connectivity. Users can log in using local credentials without requiring remote terminal access (SSH or server password access).
* **Dashboard Display** – Dashboard displays gateway identity, software version, IP addresses, current management interface, and live service status for quick health checks during on-site installs or outages.
* **Network Configuration** – Configure primary and backup management interfaces (mode, IP/subnet, gateway, DNS, VLAN) with input validation before changes are applied. Configuration persists across software upgrades and can be reverted to default at any time.
* **Diagnostics** – Built-in toolbox includes ping, traceroute, DNS lookup, and TCP/URL connectivity tests, plus a one-click Network Health Summary that runs the full diagnostic suite. Supports service restart and log bundle collection from the browser.
* **Local Password Management** – Site operators can manage LCI access credentials locally without affecting Onyx Portal credentials.
### **AP Log Collection and Storage on Onyx Edge**
Log collection and storage on Onyx Edge have been enhanced with automated and periodic RU log collection. RU onboard logs are now automatically included during techdump generation, improving diagnostic data capture and reducing manual effort. In addition, RU logs are collected periodically at a default interval of one hour, with automatic cleanup of older logs to prevent disk space exhaustion.
## 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. **No Uplink Data (PUSCH) After NR Restart** — (5G only) Following an NR server reboot/restart, the system may fail to schedule uplink PUSCH transmissions across all antennas once the NR process resumes, resulting in a complete loss of uplink user-plane traffic.\
**Workaround**: Contact GXC Technical Support to reboot the FHM and RUs together.\
This issue will be addressed in an upcoming release.
2. **Intermittent UE Attach Failure (RACH) with SRS RAN and FHM** — (5G only) In some FHM deployment scenarios, UE may randomly fail to attach to the network due to RACH failures. This issue has not been observed when the RU is directly connected to the RAN without an FHM.
**Workaround:** None.\
Direct RU connection to RAN (without FHM) avoids this issue.\
This issue will be addressed in an upcoming release.
3. **Severe UL Throughput Degradation in Multi-Cell Configuration** — (5G only) In a two-cell (inter-frequency) gNB deployment, uplink throughput may degrade by 66–73% and downlink throughput by approximately 20% compared to a single-cell deployment. Two root causes have been identified: (1) a collision between the periodicity and the measurement gap repetition period — both configured on a 40-slot cadence — leading to loss of uplink channel estimation; and (2) measurement gaps being activated unconditionally at initial RRC Reconfiguration, regardless of serving cell signal quality. Single-cell deployments are not affected.\
**Workaround:** None.\
Operating in single-cell mode avoids this issue.\
This issue will be addressed in an upcoming release.
4. **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 AP models.
**Workaround:** Restart the affected RU by performing a physical power cycle or issuing a reset command via direct login to the RU. This issue will be addressed in an upcoming release.
5. **NR Process Crash When Attaching 15+ UE** — (5G only) In some scenarios, the NR process may crash when 15 or more UE attempt to attach concurrently. Deployments operating below 15 concurrent UE attach attempts are unlikely to be affected.\
**Workaround**: None. This issue will be addressed in an upcoming release.
6. **RU Manager Exception When No Call-Home Socket Is Available** — (5G only) After an NR server reboot or power cycle, the RU Manager may encounter an unhandled exception ("No callhome socket available") while attempting to configure or reboot RUs during the startup sequence, delaying RU provisioning until the call-home connection is re-established. In most cases, provisioning recovers automatically once the call-home socket becomes available. No data-plane traffic is lost on RUs that successfully complete provisioning.
7. **MME Pool Allows Duplicate MAC Address for DHCP Server Monitoring** — (4G only) In an MME Pool, when configuring multiple Onyx Edge with DHCP Server Monitoring enabled, the system does not prevent the same MAC address from being assigned to more than one Onyx Edge, which may result in unexpected DHCP monitoring behavior.
**Workaround:** In a pooled environment, enable DHCP Server Monitoring on any one Onyx Edge, or set the MAC parameter to "Random" on all Onyx Edge in the pool. If a specific MAC address is required, ensure that each Onyx Edge in the pool is configured with a unique MAC address. This issue will be addressed in an upcoming release.
## Contact GXC
To get in touch with GXC, please visit .
---
# Agent Instructions: 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:
```
GET https://docs.gxc.io/release-notes/onyx-release-notes/onyx-4.0.0-release-notes.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.