Hyper Open Edge Cloud

FAQ

What is the difference between an ORS with and without root access?
  • Last Update:2026-09-09
  • Version:002
  • Language:en

Q: What is the difference between an ORS with and without root access?

A: By default, all ORS provided by Rapid.Space can be configured and monitored through the Rapid.Space cloud NMS (https://panel.rapid.space/), with the login provided at the delivery of the ORS product. You can access freely to this Rapid.Space NMS as long as you have open internet connection. Through the NMS platform, you can manage the radio and core-network parameters, SIM cards, device status, performance metrics, as well as reach the Rapid.Space support team directly via the integrated ticketing system. Here's a list of tutorials that you can refer to: 

In environments where an open internet connection is not available, we offer an optional offline management interface for basic device management (available on request) - a local GUI for configuring the eNB/gNB and core network, managing SIM cards, and monitoring the radio and connected UEs: https://handbook.rapid.space/ors/rapidspace-ORS.Offline.Management.System

Please note that any configuration changes made via the offline interface are temporary. Once the ORS reconnects to the main NMS, the configuration stored in the NMS will be automatically reapplied, overriding any offline changes. Additionally, historical KPI collection and remote technical support are unavailable while the ORS is operating offline. 

This default management interface is well-suited for the vast majority of standard deployments and day-to-day operations, offering both efficiency and ease of use. 

For advance users - primarily research laboratories, system integrators, and those requiring deep system-level customization, we offer root access to the underlying Linux system. Two options are available: SDK200 (maximum bandwidth 20 Mhz) and SDK600 (maximum bandwidth 50 Mhz). 

This access level allows users to directly edit Amarisoft configuration files (such as enb.cfg), start or stop services manually, and inspect system logs via the command line. Please note that this option requires solid expertise in both Linux and Amarisoft. 

Amarisoft LTE eNodeB/NR gNodeB documentation can be found here: https://tech-academy.amarisoft.com/lteenb.doc