You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The failure of the onos-a1t container shall be fine as it handles the A1 interface of the nRT-RIC. You can delete this pod through helm if you don't want to see the errors.
The current mobi-expert-xapp error is due to a bug that we find (possibly in the ONOS python SDK) which triggers an RPC error on the MobieXpert xApp. The way to get all the stuffs running would be: deploy MobiFlow Auditor -> deploy MobieXpert -> deploy gNB -> run attack.
Because of the aforementioned bug, the MobieXpert will soon crash after it receives the data through RPC. If that occurs you will have to restart the setup, i.e., the Mobiflow Auditor and MobieXpert xApps over again.
So I am trying to setup the 5G-Spector from scratch using this repo: https://github.com/5GSEC/5G-Spector/wiki/Build-5G%E2%80%90Spector-from-scratch-in-an-OAI-5G-network#iii-deploy-a-5g-network-w-rf-simulation-from-scratch
I am trying it out in a Virtual Box VM:
VM Specs:
Now when I tried deploying the mobieXpert xApp then all the containers of mobi-expert-xapp & onos-a1t are not getting in the ready state.
When i tried to describe the pods then i am getting Startup probe failed error.
Below is the screenshot for mobi-expert-xapp
Below is the screenshot for onos-a1t
I also tried to curl on the IP address of the services but I was getting connection refused error there also.
Below is the snapshot of the services
Below is the snapshot of the curl commands that I tried to execute
The text was updated successfully, but these errors were encountered: