Check if your computer is green
The first thing you should check is if your compute node on the panel is green. For this, go to your project, then find the "Compute Node" corresponding to your ORS, and then check the status button color. If it is not green, it means your ORS is not properly connected to our cloud, it could be because of firewall issue, power outage, network failure, etc...
All steps below will be completely useless if your computer status is red
Check if your service is green
If your computer status is green, you can then check the status of your service. If your service is not red, you should check the promises in the monitoring interface.
If you cannot check the promises then it is may be because your ORS is not properly connected to internet or there is a firewall issue. In any case, please create a ticket and we will support you.
Check the promises in the following order (it is important to check in the right order, you might have multiple promises failing but only one will be relevant):
Case 1: buildout-slappart9-status is red
This is likely an error due to wrong input parameters entered in the panel.
Click the promise, you should see a message like "See https://softinstXXXXXX.host.vifib.net/log/slapgrid-slappartX-error.log for more information." in the output, please then click "Access private file" and go to log/slapgrid-slappartX-error.log to check the required log, at the end of this log you should see a message indicating the issue, it is likely an issue with the frequency / band / bandwidth etc...
Case 2 : SDRX-sdr-busy is red
This means Amarisoft eNB / gNB / Core Network did not start correctly.
In that case, you check the end of the enb-info.log (or mme-info.log or ue-output.log depending on whether you are debugging eNB, MME, UE etc...), there should be an error message from Amarisoft indicating the issue.
Case 3 : SDR1-rx-saturated
This means the reception is saturated, it could be due to interferences from a nearby eNB / gNB cell (or any other device emitting in the same frequency band as you configured on your ORS), or it could be because you need to lower "RX Gain" parameter.
Case 4 : check-baseband-latency is red
This means your CPU is under high load. If you are using a Classic ORS with a Commell PC (it will be the case if you ordered it before October 2025) then you might get this error when doing 5G at 40 MHz / 50 MHz frequency because of performance limitations of your ORS computer. However unless you are running other external applications on the ORS we have tested that even though this promise is failing there won't necessarily be a noticeable performance drop on throughput for instance, so you might want to lower the threshold of this promise by updating the "Minimum available time for radio front end processing (ms)" parameter to -1