Near Realtime RIC Installation
Please check from Introduction and guides#Installingthenear-RTRIC → Installing the near-RT RIC
# Kubectl commads:
$ kubectl get pods -n nampespace - gets a list of Pods running
$ kubectl get logs -n namespace name_of_running_pod
$ kubectl get pods -n ricxapp
# View logs...
$ kubectl logs -n ricxapp <name of POD retrieved from statement above>
Comments
Hi experts,
after deployment, i have only 15 pods in ns ricplt, is it normal?
The "Step 4" says: "kubectl get pods -n ricplt # There should be ~16 pods running in the ricplt namespace.".
(18:11 dabs@ricpltbronze bin) > sudo kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-5644d7b6d9-clvtf 1/1 Running 5 32h
kube-system coredns-5644d7b6d9-jwxnm 1/1 Running 5 32h
kube-system etcd-ricpltbronze 1/1 Running 11 32h
kube-system kube-apiserver-ricpltbronze 1/1 Running 28 32h
kube-system kube-controller-manager-ricpltbronze 1/1 Running 9 32h
kube-system kube-flannel-ds-amd64-mrwn2 1/1 Running 16 32h
kube-system kube-proxy-zrtl8 1/1 Running 6 32h
kube-system kube-scheduler-ricpltbronze 1/1 Running 8 32h
kube-system tiller-deploy-68bf6dff8f-wbmwl 1/1 Running 4 32h
ricinfra deployment-tiller-ricxapp-d4f98ff65-6h4n4 1/1 Running 0 3h13m
ricinfra tiller-secret-generator-tgkzf 0/1 Completed 0 132m
ricinfra tiller-secret-generator-zcx72 0/1 Error 0 3h13m
ricplt deployment-ricplt-a1mediator-66fcf76c66-h6rp2 1/1 Running 0 40m
ricplt deployment-ricplt-alarmadapter-64d559f769-glb5z 1/1 Running 0 30m
ricplt deployment-ricplt-appmgr-6fd6664755-2mxjb 1/1 Running 0 42m
ricplt deployment-ricplt-e2mgr-8479fb5ff8-9zqbp 1/1 Running 0 41m
ricplt deployment-ricplt-e2term-alpha-bcb457df4-4dz62 1/1 Running 0 40m
ricplt deployment-ricplt-jaegeradapter-84558d855b-tmqqb 1/1 Running 0 39m
ricplt deployment-ricplt-o1mediator-d8b9fcdf-f4sgm 1/1 Running 0 34m
ricplt deployment-ricplt-rtmgr-9d4847788-kf6r4 1/1 Running 10 41m
ricplt deployment-ricplt-submgr-65dc9f4995-gt5kb 1/1 Running 0 40m
ricplt deployment-ricplt-vespamgr-7458d9b5d-klh9l 1/1 Running 0 39m
ricplt deployment-ricplt-xapp-onboarder-546b86b5c4-xkcpt 2/2 Running 0 42m
ricplt r4-infrastructure-kong-6c7f6db759-7xjqm 2/2 Running 21 3h13m
ricplt r4-infrastructure-prometheus-alertmanager-75dff54776-jfkdg 2/2 Running 2 3h13m
ricplt r4-infrastructure-prometheus-server-5fd7695-pprg2 1/1 Running 2 3h13m
ricplt statefulset-ricplt-dbaas-server-0 1/1 Running 0 43m
After deployment I'm also getting only 15 pods running. Is it normal or do I need to worry about that?
it's normal, and you are good to go. just try policy management.
Hi,
Even though deployment of RIC plt did not give any errors, most of the RIC plt and infra pods remain in error state.
kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system coredns-5644d7b6d9-dz774 1/1 Running 1 10h
kube-system coredns-5644d7b6d9-fp586 1/1 Running 1 10h
kube-system etcd-ggnlabvm-bng35 1/1 Running 1 10h
kube-system kube-apiserver-ggnlabvm-bng35 1/1 Running 1 10h
kube-system kube-controller-manager-ggnlabvm-bng35 1/1 Running 1 10h
kube-system kube-flannel-ds-amd64-b4l97 1/1 Running 1 10h
kube-system kube-proxy-fxfrk 1/1 Running 1 10h
kube-system kube-scheduler-ggnlabvm-bng35 1/1 Running 1 10h
kube-system tiller-deploy-68bf6dff8f-jvtk7 1/1 Running 1 10h
ricinfra deployment-tiller-ricxapp-d4f98ff65-hcnqf 0/1 ContainerCreating 0 9h
ricinfra tiller-secret-generator-d7kmk 0/1 ImagePullBackOff 0 9h
ricplt deployment-ricplt-a1mediator-66fcf76c66-l2z7m 0/1 ImagePullBackOff 0 9h
ricplt deployment-ricplt-alarmadapter-64d559f769-7d8fq 0/1 ImagePullBackOff 0 9h
ricplt deployment-ricplt-appmgr-6fd6664755-7lp8q 0/1 Init:ImagePullBackOff 0 9h
ricplt deployment-ricplt-e2mgr-8479fb5ff8-ggnx8 0/1 ErrImagePull 0 9h
ricplt deployment-ricplt-e2term-alpha-bcb457df4-dkdbc 0/1 ImagePullBackOff 0 9h
ricplt deployment-ricplt-jaegeradapter-84558d855b-bpzcv 1/1 Running 0 9h
ricplt deployment-ricplt-o1mediator-d8b9fcdf-5ptcs 0/1 ImagePullBackOff 0 9h
ricplt deployment-ricplt-rtmgr-9d4847788-rvnrx 0/1 ImagePullBackOff 0 9h
ricplt deployment-ricplt-submgr-65dc9f4995-cbhvc 0/1 ImagePullBackOff 0 9h
ricplt deployment-ricplt-vespamgr-7458d9b5d-bkzpg 0/1 ImagePullBackOff 0 9h
ricplt deployment-ricplt-xapp-onboarder-546b86b5c4-g2dnt 1/2 ImagePullBackOff 0 9h
ricplt r4-infrastructure-kong-6c7f6db759-4czbj 2/2 Running 2 9h
ricplt r4-infrastructure-prometheus-alertmanager-75dff54776-gwxzz 2/2 Running 0 9h
ricplt r4-infrastructure-prometheus-server-5fd7695-phcqs 1/1 Running 0 9h
ricplt statefulset-ricplt-dbaas-server-0 0/1 ImagePullBackOff 0 9h
any clue?
The ImagePullBackOff and ErrrImagePull errors are all for container images built from O-RAN SC code. It appears that there is a problem for the docker engine in your installation fetching images from the O-RAN SC docker registry. Oftentimes this is due to local firewall blocking such connections.
You may want to try: docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-a1:2.1.9 to see if your docker engine can retrieve this image.
Thanks for the information.
I think you are right, even docker pull nexus3.o-ran-sc.org:10002/o-ran-sc/ric-plt-a1:2.1.9 is giving an error of connection refused..
although I am checking for the corporate firewall to disable it, the strange thing is docker pull hello-world and other such pulls are working fine.
"Connection refused" error does suggest network connection problem.
These O-RAN SC docker registries use port 10001 ~ 10004, in particular 10002 for all released docker images. They are not the default docker registry of 5000. It is possible that your local firewall has a rule allowing outgoing connections into port 5000, but not these ports.
Thanks for the explanation. you are right these ports were blocked on firewall, working fine now.
currently i am stuck with opening o1 dashboard, trying it on smo machine.
thanks for the explanation. you are right these particular ports were getting blocked by firewall, got it working now.
currently i am stuck in opening o1 dashboard, trying it on smo machine.
Hi Team,
Can you please share the link so that i am able to download the docker image manually and then load the same. I am also getting connection refused but not able to solve this thing. Meanwhile plz share the link so that it will help for me.
Br
Deepak
Thanks for the guidelines. It works well.