O-RAN Profile

102 views
Skip to first unread message

Leo Zidane

unread,
Dec 18, 2021, 10:48:27 AM12/18/21
to Powder Users
i tried to  Onboard the scp-kpimon xApp in node 0 but encountered an error "Undefined variable."

Did I key in the commands correctly indicated in the O-RAN Profile?

Thank you


Capture.PNG

David M. Johnson

unread,
Dec 18, 2021, 11:40:21 AM12/18/21
to powder...@googlegroups.com
>From the screenshot, looks like your shell is tcsh. Before running any
of the commands, please run `bash` first. (Or if you need to use tcsh,
you can use setenv instead.)

David
Message has been deleted

Leo Zidane

unread,
Dec 19, 2021, 1:22:42 AM12/19/21
to Powder Users
I have executed bash below using the commands in the profile. It works but I have an error when viewing the logs.

Deploy the scp-kpimon xApp:
curl -L -X POST         "http://${KONG_PROXY}:32080/appmgr/ric/v1/xapps"         --header 'Content-Type: application/json'         --data-raw '{"xappName": "scp-kpimon"}'
View the logs of the scp-kpimon xApp:
kubectl logs -f -n ricxapp -l app=ricxapp-scp-kpimon

leonard@node-0:~$ kubectl logs -f -n ricxapp -l app=ricxapp-scp-kpimon
Error from server (BadRequest): container "scp-kpimon-xapp" in pod "ricxapp-scp-kpimon-5f88485758-9ppfq" is waiting to start: trying and failing to pull image
leonard@node-0:~$

Leo Zidane

unread,
Dec 19, 2021, 11:28:47 AM12/19/21
to Powder Users
Still having Kpimon error unable to view the logs:

node-0:~> bash
leonard@node-0:~$ export KONG_PROXY=`kubectl get svc -n ricplt -l app.kubernetes                                                                                                    .io/name=kong -o jsonpath='{.items[0].spec.clusterIP}'`
leonard@node-0:~$ curl -L -X POST         "http://${KONG_PROXY}:32080/onboard/ap                                                                                                    i/v1/onboard/download"         --header 'Content-Type: application/json'                                                                                                             --data-binary "@/local/profile-public/scp-kpimon-onboard.url"
{
    "status": "Created"
}
leonard@node-0:~$ curl -L -X GET         "http://${KONG_PROXY}:32080/onboard/api                                                                                                    /v1/charts"
{
    "nexran": [
        {
            "name": "nexran",
            "version": "0.1.0",
            "description": "Standard xApp Helm Chart",
            "apiVersion": "v1",
            "appVersion": "1.0",
            "urls": [
                "charts/nexran-0.1.0.tgz"
            ],
            "created": "2021-12-19T08:52:11.927944962Z",
            "digest": "b263357e2d5caf3a3507cc6d609fc797f45eccdad7cd8c34b315ed022                                                                                                    4423052"
        }
    ],
    "scp-kpimon": [
        {
            "name": "scp-kpimon",
            "version": "1.0.1",
            "description": "Standard xApp Helm Chart",
            "apiVersion": "v1",
            "appVersion": "1.0",
            "urls": [
                "charts/scp-kpimon-1.0.1.tgz"
            ],
            "created": "2021-12-19T16:15:07.948553178Z",
            "digest": "68a6a087019298dfb91bbc28fad0b8e73b4e666a8860a8c7a920383a0                                                                                                    3ce4140"
        }
    ]
}
leonard@node-0:~$ curl -L -X POST         "http://${KONG_PROXY}:32080/appmgr/ric/v1/xapps"         --header 'Content-Type: application/json'         --data-raw '{"xappName": "scp-kpimon"}'

leonard@node-0:~$ kubectl logs -f -n ricxapp -l app=ricxapp-scp-kpimon
Error from server (BadRequest): container "scp-kpimon-xapp" in pod "ricxapp-scp-kpimon-5f88485758-9ppfq" is waiting to start: trying and failing to pull image
leonard@node-0:~$ kubectl logs -f -n ricxapp -l app=ricxapp-scp-kpimon
Error from server (BadRequest): container "scp-kpimon-xapp" in pod "ricxapp-scp-kpimon-5f88485758-9ppfq" is waiting to start: trying and failing to pull image
leonard@node-0:~$ kubectl logs -f -n ricxapp -l app=ricxapp-scp-kpimon
Error from server (BadRequest): container "scp-kpimon-xapp" in pod "ricxapp-scp-kpimon-5f88485758-9ppfq" is waiting to start: trying and failing to pull image
leonard@node-0:~$ kubectl logs -f -n ricxapp -l app=ricxapp-scp-kpimon
Error from server (BadRequest): container "scp-kpimon-xapp" in pod "ricxapp-scp-kpimon-5f88485758-9ppfq" is waiting to start: trying and failing to pull image
leonard@node-0:~$ kubectl logs -f -n ricxapp -l app=ricxapp-scp-kpimon
Error from server (BadRequest): container "scp-kpimon-xapp" in pod "ricxapp-scp-kpimon-5f88485758-9ppfq" is waiting to start: trying and failing to pull image
leonard@node-0:~$

David M. Johnson

unread,
Dec 20, 2021, 8:02:34 PM12/20/21
to powder...@googlegroups.com
On 12/18/21 11:19 PM, Leo Zidane wrote:
> With the bash command I can execute but face some errors: 
>
> leonard@node-0:~$ kubectl logs -f -n ricxapp -l app=ricxapp-scp-kpimon  
>        Error from server (BadRequest): container "scp-kpimon-xapp" in
> pod "ricxapp-scp-kpimon-5f88485758-9ppfq" is waiting to start: image
> can't be pulled
> leonard@node-0:~$ kubectl logs -f -n ricxapp -l app=ricxapp-scp-kpimon
> Error from server (BadRequest): container "scp-kpimon-xapp" in pod
> "ricxapp-scp-kpimon-5f88485758-9ppfq" is waiting to start: image can't
> be pulled
> leonard@node-0:~$

Hi Leo. One of the build deps for our patched version of the scp-kpimon
app was removed from the upstream registry, so the build was failing. I
tweaked the profile to pull cached build images for our custom
components, so you should no longer have this issue. (We had patched
the kpimon xapp because it was broken back in the bronze/cherry era, but
we need to revisit because I think those fixes were merged up. It's on
my list.)

David

Leo Zidane

unread,
Dec 21, 2021, 5:53:56 AM12/21/21
to Powder Users
Hi David,

I try to execute the command below (Deploy the scp-kpimon xApp:) but there is an error.
  • curl -L -X POST "http://${KONG_PROXY}:32080/appmgr/ric/v1/xapps" --header 'Content-Type: application/json' --data-raw '{"xappName": "scp-kpimon"}'

node-0:~> curl -L -X POST         "http://${KONG_PROXY}:32080/appmgr/ric/v1/xapps"         --header 'Content-Type: application/json'         --data-raw '{"xappName": "scp-kpimon"}'
KONG_PROXY: Undefined variable.
node-0:~>

leonard@node-0:~$ curl -L -X POST         "http://${KONG_PROXY}:32080/appmgr/ric/v1/xapps"         --header 'Content-Type: application/json'         --data-raw '{"xappName": "scp-kpimon"}'
curl: (6) Could not resolve host:
leonard@node-0:~$

David M. Johnson

unread,
Dec 21, 2021, 9:53:42 AM12/21/21
to powder...@googlegroups.com
On 12/21/21 3:53 AM, Leo Zidane wrote:
> Hi David,
>
> I try to execute the command below (Deploy the scp-kpimon xApp:) but
> there is an error.
>
> * curl -L -X POST "http://${KONG_PROXY}:32080/appmgr/ric/v1/xapps"
> --header 'Content-Type: application/json' --data-raw '{"xappName":
> "scp-kpimon"}'
>
>
> node-0:~> curl -L -X POST        
> "http://${KONG_PROXY}:32080/appmgr/ric/v1/xapps"         --header
> 'Content-Type: application/json'         --data-raw '{"xappName":
> "scp-kpimon"}'
> KONG_PROXY: Undefined variable.
> node-0:~>
>
> leonard@node-0:~$ curl -L -X POST        
> "http://${KONG_PROXY}:32080/appmgr/ric/v1/xapps"         --header
> 'Content-Type: application/json'         --data-raw '{"xappName":
> "scp-kpimon"}'
> curl: (6) Could not resolve host:
> leonard@node-0:~$

Any chance you changed to `bash` after having set KONG_PROXY in tcsh?
You need to re-run the preceeding commands to set KONG_PROXY after
switching to bash.

David
> --
> You received this message because you are subscribed to the Google
> Groups "Powder Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to powder-users...@googlegroups.com
> <mailto:powder-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/powder-users/c2426a97-717e-4f4c-a790-7339eb340689n%40googlegroups.com
> <https://groups.google.com/d/msgid/powder-users/c2426a97-717e-4f4c-a790-7339eb340689n%40googlegroups.com?utm_medium=email&utm_source=footer>.

Leo Zidane

unread,
Dec 21, 2021, 11:19:50 AM12/21/21
to Powder Users
I open a ssh terminal and executed the below commands on node 0

node-0:~> bash
leonard@node-0:~$ ion.
ion.: command not found
leonard@node-0:~$ export KONG_PROXY=`kubectl get svc -n ricplt -l app.kubernetes.io/name=kong -o jsonpath='{.items[0].spec.clusterIP}'`
leonard@node-0:~$ curl -L -X POST         "http://${KONG_PROXY}:32080/onboard/api/v1/onboard/download"         --header 'Content-Type: application/json'         --data-binary "@/local/profile-public/scp-kpimon-onboard.url"
{
    "status": "Created"
}
leonard@node-0:~$ curl -L -X GET         "http://${KONG_PROXY}:32080/onboard/api/v1/charts"

{
    "nexran": [
        {
            "name": "nexran",
            "version": "0.1.0",
            "description": "Standard xApp Helm Chart",
            "apiVersion": "v1",
            "appVersion": "1.0",
            "urls": [
                "charts/nexran-0.1.0.tgz"
            ],
            "created": "2021-12-21T10:48:29.791532626Z",
            "digest": "7017d6110fe00fc2a76b85e1f102721360056f79f00f8440d09f94f6b5e89801"

        }
    ],
    "scp-kpimon": [
        {
            "name": "scp-kpimon",
            "version": "1.0.1",
            "description": "Standard xApp Helm Chart",
            "apiVersion": "v1",
            "appVersion": "1.0",
            "urls": [
                "charts/scp-kpimon-1.0.1.tgz"
            ],
            "created": "2021-12-21T16:13:59.476198778Z",
            "digest": "97a99943f7a28ec2dc90d0a0e456832242199af0de0cb24f89f8bb83a7ec1529"
        }
    ]

}
leonard@node-0:~$ curl -L -X POST         "http://${KONG_PROXY}:32080/appmgr/ric/v1/xapps"         --header 'Content-Type: application/json'         --data-raw '{"xappName": "scp-kpimon"}'
{"instances":null,"name":"scp-kpimon","status":"deployed","version":"1.0"}
leonard@node-0:~$ kubectl exec -it -n ricxapp `kubectl get pod -n ricxapp -l app=ricxapp-scp-kpimon -o jsonpath='{.items[0].metadata.name}'` -- tail -F /opt/kpimon.log
[qSkipTool]2021/12/21 16:14:20 control.go:67: Failed to connect to Redis DB with dial tcp 127.0.0.1:6379: connect: connection refused
[qSkipTool]2021/12/21 16:14:33 control.go:89: send RIC_SUB_REQ to gNodeB with cnt=1
[qSkipTool]2021/12/21 16:14:33 control.go:1072: Set EventTriggerDefinition: 2034000000000000
[qSkipTool]2021/12/21 16:14:33 control.go:1105: Send RIC_SUB_REQ to {enB_macro_001_001_0019b0}
[qSkipTool]2021/12/21 16:14:33 control.go:1115: Set Payload: 00080028000003001d00050003e903e9000500020000001e0012000820340000000000000000130003000000
[qSkipTool]2021/12/21 16:14:33 control.go:1119: The RMR message to be sent is 12010 with SubId=1001
[qSkipTool]2021/12/21 16:14:33 control.go:986: RIC_SUB_REQ[enB_macro_001_001_0019b0]: Waiting for RIC_SUB_RESP...
[qSkipTool]2021/12/21 16:14:38 control.go:996: RIC_SUB_REQ[enB_macro_001_001_0019b0]: RIC Event Create Timer experied!


After that I opened another ssh terminal to node 0 to execute the  "sudo ip netns exec ue1 ping 192.168.0.1"

leonard@node-0:~$ sudo ip netns exec ue1 ping 192.168.0.1
connect: Network is unreachable
leonard@node-0:~$

David M. Johnson

unread,
Dec 21, 2021, 12:01:05 PM12/21/21
to powder...@googlegroups.com
Could be multiple things going on here, but one thing I saw when I
looked through your bash command history on your experiment node was
that there were no logged invocations of `srsepc`. You'll want to run
the epc before you fire up srsenb and srsue.

The failure of the xApp to subscribe could be that srsenb wasn't
running, or that you ran into a bug/missing feature with the `submgr`.
Historically the submgr doesn't automatically delete subscriptions to
RAN nodes when those RAN nodes disconnect from the e2term (this is what
happens when you kill/restart srsenb). This feature has now been added
for the `e` release, I believe, but it didn't make it into the `d`
release. So -- every time you kill your srsenb, if you had an xApp
running, before starting the srsenb back up, you'll want to restart your
submgr (`kubectl -n ricplt rollout restart deployment
deployment-ricplt-submgr`), wait for it to restart and reestablish its
routes with rmr (by observing its pods' log output), then restart your
srsenb. Neither the scp-kpimon nor nexran xApps handles that situation,
so you'll have to restart them, too. If you don't want to mess with the
submgr, you can also just use the instructions to undeploy/redeploy your
entire RIC, and start from the top of the instructions.

David
Reply all
Reply to author
Forward
0 new messages