gradiant / 5g-charts Goto Github PK

View Code? Open in Web Editor NEW

64.0 64.0 40.0 4.01 MB

Helm charts for 5G Technologies

License: Apache License 2.0

Shell 7.12% Smarty 77.66% Makefile 8.27% Mustache 6.95%

5g-charts's People

Contributors

Stargazers

Watchers

5g-charts's Issues

NAT rule in UPF/open5gs is not working

I can see that upf has NAT rule set as default,
but there is iptables, iptables-legacy both working.

therefore, ping from ue(ueransim-gnb) to 8.8.8.8 does not work.

UPF:
iptables -L -t nat

root@open5gs-upf-0:~# iptables -L -t nat
# Warning: iptables-legacy tables present, use iptables-legacy to see them
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination         

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination         
MASQUERADE  all  --  10.45.0.0/16         anywhere

iptables-legacy -L -t nat

root@open5gs-upf-0:~# iptables-legacy -L -t nat
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination         

Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination

after setting iptables-legacy -t nat -A POSTROUTING -s 10.45.0.0/16 ! -o ogstun -j MASQUERADE, it works.

I worder if I can put nat rule for iptables-legacy in helm chart so I don't need to put it manually,
or is there a way I can remove iptables-legacy.

Additionally, I want to know if this issue is appearing only for me.
Thanks in advance.

Open5gs 2.6 release not included in Openverso charts

Hello team!

I am currently working in R&D at Dish Network. We aim to build a reinforcement learning agent to scale UPF's.

An issue we are currently facing is that PDU sessions do not transfer over from an UPF (if that UPF gets deleted or removed) to a new UPF via SMF. This is an issue in 2.4 that is patched in 2.6.

Can Openverso please upgrade Open5gs to 2.6 to enable users with this new functionality? We would like the 2.6 version helm charts to be included as part of Openverso.

Respectfully, Vinayak

I can't make UE from UERANSIM work with open5gs, both openverso-charts

So i ping for exemple google.com and it's 100% package lost
I used your configs and only changed the version to 3.2.4, 3.2.2 didn t work either.
I can't find the reason why this is not working with open5gs tag latest

Can you help plz?

Open5gs -CrashLoopBackOff after first installation

Hi!

I was able to install and perform data traffic test in first installation. But after this I am trying to install again and I suffer some issues and not all pods are created correctly.

After some checks I dont see the issue and I know some collegues had similar issues. Maybe you know some reason or key info.¿?

On the other hand I was able to launch 3 UPFs modifying HPA to 3 as maxium. This is suppose to course traffic in any of 3 UPFs in a high availability scenario. In theory it should be possible even without modify config SMF info, but I dont know if any know something about this test.
Additionally with Rolling Update if any config change is done it should hav no downtime.

Do you have any help for any of 2 topics? Thanks in advance!

And congrats for the doc effort.BR

SMF connection issues

When trying to connect a UE from UERANSIM, it's failing on one step which I think is related to the SMF not connecting. Below are the logs from the various NFs:

SMF (logs seem fine):
04/11 21:50:57.156: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/smf.yaml' (../lib/app/ogs-init.c:129)
04/11 21:50:57.275: [gtp] INFO: gtp_server() [10.1.59.79]:2123 (../lib/gtp/path.c:30)
04/11 21:50:57.275: [gtp] INFO: gtp_server() [10.1.59.79]:2152 (../lib/gtp/path.c:30)
04/11 21:50:57.275: [pfcp] INFO: pfcp_server() [10.1.59.79]:8805 (../lib/pfcp/path.c:30)
04/11 21:50:57.275: [pfcp] INFO: ogs_pfcp_connect() [10.152.183.161]:8805 (../lib/pfcp/path.c:59)
04/11 21:50:57.275: [sbi] INFO: nghttp2_server() [10.1.59.79]:7777 (../lib/sbi/nghttp2-server.c:144)
04/11 21:50:57.275: [app] INFO: SMF initialize...done (../src/smf/app.c:31)
04/11 21:50:57.276: [smf] INFO: PFCP associated (../src/smf/pfcp-sm.c:174)
04/11 21:50:57.279: [smf] INFO: [77e345b2-b9e1-41ec-bf78-4322aa4ff042] NF registred [Heartbeat:10s] (../src/smf/nf-sm.c:199)
04/11 21:50:58.755: [pfcp] INFO: ogs_pfcp_connect() [10.1.59.12]:8805 (../lib/pfcp/path.c:59)
04/11 21:50:58.755: [smf] INFO: PFCP associated (../src/smf/pfcp-sm.c:174)
04/11 21:50:59.301: [diam] INFO: CONNECTED TO 'pcrf.openverso' (SCTP,soc#22): (../lib/diameter/common/logger.c:108)

UE:
[2022-04-12 15:27:11.167] [nas] [info] UE switches to state [MM-REGISTERED/NORMAL-SERVICE]
[2022-04-12 15:27:11.167] [nas] [debug] Sending Registration Complete
[2022-04-12 15:27:11.167] [nas] [info] Initial Registration is successful
[2022-04-12 15:27:11.167] [nas] [debug] Sending PDU Session Establishment Request
[2022-04-12 15:27:11.167] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]
[2022-04-12 15:27:11.376] [nas] [debug] Configuration Update Command received
[2022-04-12 15:27:21.386] [nas] [error] SM forwarding failure for message type[193] with cause[PAYLOAD_NOT_FORWARDED]
[2022-04-12 15:27:21.386] [nas] [debug] Aborting SM procedure for PTI[1], PSI[1]
[2022-04-12 15:27:22.157] [nas] [debug] Sending PDU Session Establishment Request
[2022-04-12 15:27:22.157] [nas] [debug] UAC access attempt is allowed for identity[0], category[MO_sig]

NRF:
04/11 21:45:51.860: [nrf] WARNING: [af541f04-b9e0-41ec-88da-514d16886d4a] No heartbeat (../src/nrf/nrf-sm.c:228)

UPF:
04/11 21:50:57.275: [pfcp] INFO: ogs_pfcp_connect() [10.1.59.79]:8805 (../lib/pfcp/path.c:59)
04/11 21:50:57.276: [upf] INFO: PFCP associated (../src/upf/pfcp-sm.c:173)
04/11 21:50:58.755: [upf] WARNING: Retry to association with peer [10.152.183.178]:8805 failed (../src/upf/pfcp-sm.c:106)
04/11 21:50:58.755: [upf] INFO: PFCP associated (../src/upf/pfcp-sm.c:173)
04/11 21:51:02.250: [pfcp] WARNING: [54974] LOCAL No Reponse. Give up! for step 1 type 1 peer [10.1.59.8]:8805 (../lib/pfcp/xact.c:618)
04/11 21:51:02.250: [upf] WARNING: No Heartbeat from SMF [10.1.59.8]:8805 (../src/upf/pfcp-sm.c:256)
04/11 21:51:02.250: [upf] INFO: PFCP de-associated (../src/upf/pfcp-sm.c:178)

AMF:
04/11 22:03:36.035: [gmm] INFO: UE SUPI[imsi-999700000000001] DNN[internet] S_NSSAI[SST:1 SD:0xffffff] (../src/amf/gmm-handler.c:1047)
04/11 22:03:39.091: [sbi] WARNING: [7] Failed to connect to 10.1.59.8 port 7777: No route to host (../lib/sbi/client.c:484)
04/11 22:03:46.039: [amf] ERROR: [1:0] Cannot receive SBI message (../src/amf/amf-sm.c:584)
04/11 22:03:46.039: [amf] WARNING: [suci-0-999-70-0000-0-0-0000000001] DL NAS transport (../src/amf/nas-path.c:573)

I'm not sure where the 10.1.59.8 address is coming from (not configured for any of the Core NFs), but according to UPF logs, it seems like it thinks that IP is for the SMF.

According to https://open5gs.org/open5gs/docs/troubleshoot/02-now-in-github-issues/, that error points to running the SMF without the NRF:

However, among these, SMF and UPF are used by both 4G EPC and 5G Core. And SMF has a protocol stack to interact with 5G NRF. Therefore, if you run SMF without running 5G NRF, the following WARNING occurs in SMF.

10/08 14:44:03.045: [sbi] WARNING: [7] Failed to connect to ::1 port 7777: Connection refused (../lib/sbi/client.c:450)
10/08 14:44:03.045: [smf] INFO: PFCP associated (../src/smf/pfcp-sm.c:174)
10/08 14:44:03.046: [diam] INFO: CONNECTED TO 'pcrf.localdomain' (SCTP,soc#16): (../lib/diameter/common/logger.c:108)
10/08 14:44:06.046: [smf] WARNING: [3c85dd06-0996-41eb-a985-476fa905aefc] Retry to registration with NRF (../src/smf/nf-sm.c:161)
10/08 14:44:06.047: [sbi] WARNING: [7] Failed to connect to ::1 port 7777: Connection refused (../lib/sbi/client.c:450)

Any ideas on why the SMF is getting assigned this .8 IP?

Ser resource limits when deploying the chart

Hi!
Thanks for such a great 5g chart!
Following your tutorial, I can successfully deploy the k8s 5g and test its performance.
I have an extra need to set the resource limits that can be used by each pod.
Could you please give me some suggestions on how to add these resource parameters when deploying the charts using value.yaml?
Thanks a lot!

Get various hostnames with smf-upf-pfcp values config

Hello!

I had success in launch an additional UPF usign OpenVerso charts, and changing config values from outside. This is a great job and allow me to use different configuration from base chart.

But actually , I have the following problem, when I update with 'helm upgrade...' as follows:

helm upgrade open5gs open5gs --values new-config-2dnn.yaml

The part of SMF config gets only the last Hostname define (in the case below 'internet2'

...
smf:
config:
pcrf:
enabled: false

subnetList:
  - addr: 10.45.0.1/16
    dnn: internet
  - addr: 10.46.0.1/16
    dnn: internet2
upf:      
  pfcp:
    hostname: "open5gs-upf-pfcp"
    dnn: internet
    hostname: "open5gs-upf2-pfcp"
    dnn: internet2

...

Maybe it is needed to change something in the values config map to allow to get both hostnames?? I hope you can check if there is any issue to get both upf-pfcp--> 2xhostnames

Thanks in advance!

Certificates of hss,mme and pcrfr pods is expired when changed tag to latest

So i tried to change the replicasets to latest tag and in the pods it says that The certificate is expired(mme,hss and pcrf).
`
2022/01/24 13:26:22.0510: [ 1]: WARNING: mongoc: Falling back to malloc for counters.

24/1/2022 13:26:22 | Open5GS daemon v2.3.3

24/1/2022 13:26:22 | 01/24 13:26:22.514: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/pcrf.yaml' (../lib/app/ogs-init.c:129)

24/1/2022 13:26:22 | 01/24 13:26:22.518: [dbi] INFO: MongoDB URI: 'mongodb://open5gs-mongodb/open5gs' (../lib/dbi/ogs-mongoc.c:130)

24/1/2022 13:26:22 | 01/24 13:26:22.523: [diam] ERROR: pid:Main in [email protected]:465: - The certificate is expired.

24/1/2022 13:26:22 | ((null):0)

24/1/2022 13:26:22 | 01/24 13:26:22.523: [diam] ERROR: pid:Main in [email protected]:245: ERROR: in
'((fd_conf_parse()))' : Invalid argument

24/1/2022 13:26:22 | ((null):0)

24/1/2022 13:26:22 | 01/24 13:26:22.523: [diam] ERROR: pid:Main in [email protected]:49: ERROR: in '(fd_core_parseconf(conffile))' : Invalid argument

24/1/2022 13:26:22 | ((null):0)

24/1/2022 13:26:22 | 01/24 13:26:22.625: [pcrf] FATAL: pcrf_fd_init: Assertion `rv == 0' failed. (../src/pcrf/pcrf-fd-path.c:29)

24/1/2022 13:26:22 | 01/24 13:26:22.625: [core] FATAL: backtrace() returned 7 addresses (../lib/core/ogs-abort.c:37)
24/1/2022 13:26:22 | open5gs-pcrfd(+0x67d8) [0x5649f1ca17d8]

24/1/2022 13:26:22 | open5gs-pcrfd(+0x5085) [0x5649f1ca0085]

24/1/2022 13:26:22 | open5gs-pcrfd(+0x4736) [0x5649f1c9f736]

24/1/2022 13:26:22 | open5gs-pcrfd(+0x4f0e) [0x5649f1c9ff0e]

24/1/2022 13:26:22 | /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f4ea0c74d0a]

24/1/2022 13:26:22 | open5gs-pcrfd(+0x466a) [0x5649f1c9f66a]

Is there any network limitations on the Open5GS?

I'm currently testing the open5GS network using an iperf3 client on a user equipment and an external iperf server located outside the cluster. I'm experiencing maximum rate peaks of 380 Mbits per second. Do you have any suggestions on where to search for limitations?

PS: No network policies in the cluster or CPU and memory limitations on containers.

Metrics not supported?

Hi, I'm trying to access the NF metrics (https://open5gs.org/open5gs/docs/tutorial/04-metrics-prometheus/), and I see that the helm chart takes an argument for (containerPorts.metrics int, default is 9090). However the NF containers, in their yaml config files do not contain any mention of metrics, and running prometheus I can't scrap anything from the default ports (9090).
Are metrics supported at all in this chart?

I'm using the latest version from openverso https://gradiant.github.io/openverso-charts/

UPF does not forward returned packets to the gnb

Hi. I deployed these charts on aws eks, and everything seems to work fine except the NAT. I see the packets go out the upf to the internet but the responses don't make it back to the gnb or ue. Any ideas?

Issue with SMF pod

Hello,

I'm trying to deploy open5GS helm charts for 5G using this repository: https://github.com/Gradiant/openverso-charts and deploying the helms present in the folder 'openverso-charts/charts/open5gs'.
I have all the pods running with the exception of SMF, which is generating the following logs:

Open5GS daemon v2.5.6

01/04 11:39:08.987: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/smf.yaml' (../lib/app/ogs-init.c:126)
01/04 11:39:09.010: [metrics] INFO: Prometheus mhd_server() [0.0.0.0]:9090 (../lib/metrics/prometheus/context.c:320)
01/04 11:39:09.038: [diam] ERROR: pid:Main in [email protected]:69: /opt/open5gs/etc/freeDiameter/smf.conf:266.65 : Name or service not known
((null):0)
01/04 11:39:09.038: [diam] ERROR: pid:Main in [email protected]:69: /opt/open5gs/etc/freeDiameter/smf.conf:266.65 : An error occurred while parsing the configuration file
((null):0)
01/04 11:39:09.038: [diam] ERROR: pid:Main in [email protected]:281: ERROR: in '((fddparse(fd_g_config)))' : Invalid argument
((null):0)
01/04 11:39:09.038: [diam] ERROR: pid:Main in [email protected]:245: ERROR: in '((fd_conf_parse()))' : Invalid argument
((null):0)
01/04 11:39:09.038: [diam] ERROR: pid:Main in [email protected]:49: ERROR: in '(fd_core_parseconf(conffile))' : Invalid argument
((null):0)
01/04 11:39:09.039: [smf] FATAL: smf_fd_init: Assertion `rv == 0' failed. (../src/smf/fd-path.c:36)
01/04 11:39:09.039: [core] FATAL: backtrace() returned 7 addresses (../lib/core/ogs-abort.c:37)
open5gs-smfd(+0x43173) [0x563bc255a173]
open5gs-smfd(+0xd42e) [0x563bc252442e]
open5gs-smfd(+0xc8c6) [0x563bc25238c6]
open5gs-smfd(+0xd140) [0x563bc2524140]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f2d356f4d0a]
open5gs-smfd(+0xc7fa) [0x563bc25237fa]
/entrypoint.sh: line 41: 7 Aborted (core dumped) $@

Any suggestion on how to solve this issue?

Thank you very much in advance,
Best regards,
João Silva

Run the pods with Privileges

Hi!
I want to run some of the NFs with Privileges. I add containerSecurityContext to AMF in the vaule.yaml while deploying the open5gs, referring the the settings of UPF, since in the created UPF pod I can use tc to inject some network faults to see the 5g core's performace.
But in the AMF pod, I cannot use the tc command due to privileges.
After I add containerSecurityContext to give AMF the privileges, the tc command still fail.
Could you please tell me how to set the the configurations to run AMF as a previleged pod?
Thanks in advance.

Upgrade Open5GS to 2.6.1 version failed

info query - root password for containers (nrf, nssf, pcf, udm, ...)

Hi,
not an issue, just info query.
i wanted to install some packages on some pods/containers (mainly tcpdump for traffic inspection). I can instal it on on upf, since i can sudo there. But for rest of pods, it does not allowed me. And i don't know root password on those.
Is there a way to install some packages on those pods (root password ?)
Kudos for great work done !
thanks

ingressClassName not used in webui ingress template

Hello!
I was trying to configure the ingress service for webui as nginx type. I have seen that the variable ingressClassName is defined in the values.yaml of webui/templates but then it is not used in webui/templates/ingress.yaml.

Correct me if I'm wrong, but I think there is a line missing in the charts/open5gs-webui/templates/ingress.yaml file.

spec:
  ingressClassName: ... (to add)
  rules:
    - host: {{ .Values.ingress.hostname | default (printf "%s-%s.ingress.lab5g.gradiant.org" .Release.Name .Release.Namespace) }}

If not, please, could you help me with this ingress type nginx?

Thanks,
Anabel

Needed last version of Open5GS in order to use frame routing

Issue in Open5GS SBI

Hello,

I've deployed Open5GS in kubernetes using this repository:
https://github.com/Gradiant/openverso-charts
All pods are successfully deployed but I'm getting the following for the PCF component:

Do you have a suggestion on how to solve this issue?

Thank you very much for the attention,
Best regards,
João Silva

Expose upf and amf services to external gnodeb

Hello, thanks for the great work! I'm using this charts and I would like to use external gnodeb so I want to connect it with the core. I suppose that I need to expose N3 and N2 interfaces between gnodeb and the k8s cluster. I have no loadbalancer at the moment.
Do I need to expose the service like node-port instead ClusterIP and probably those one related to UPF and AMF like open-5gs-upf-pfcp,open-5gs-upf-gtpu and open5gs-amf-ngap, open5gs-amf-sbi? It will work?
Thanks :)

On ueransim gnb is running but ue fails

it says: [rls-udp] [error] Unable to decode RLS message

How do we test this(ueransim) on our kubernetes cluster with open5gs??
Running kubernetes cluster with open5gs(latest version) and ueransim(version 3.2.4) in same namespace from your helm chart

Bug when adding new User Equipment [default sd is not 0x111111]

Hello
I'm not sure why, but when I deploy your helm charts (using Open5GS and ueransim-ues), the AMF from Open5gs rejects it because it doesn't recognize the sd of the ue. Hence, in order for it to function, I have to manually add the sd to the mongodb database.
I didn't alter any of your chart values.

open5gs with multus

Hi,
first thanks for great work on open5gs charts.
This is not really an issue but kind request for help.
I'd like to split control&data traffic via mutliple interfaces (ie. N3, N6 for UPF). Perhaps I can manage on adding multus, preparing NetworkAttachmentDefinitions, pod annotations) but not rally sure on how to reflect changes in chart manifests (interfaces referenced, IP addresses of components to be static or dynamic, vs hostnames).
I could not find some references inside charts (beside mentioning interface for some components).
Do you have some guidelines on how to introduce separation of traffic types with multus ?

What is the password for the root of the container Open5gs

Not able to install some iperft on open5gs-am
i try to add a user but i dont have the password

have no name!@open5gs-amf-66f6857b9f-6hv99:~$ su
Password:

I have no name!@open5gs-amf-66f6857b9f-6hv99:~$

Getting the "SCTP could not connect: Operation timed out" Error

I'm following your tutorial for the Open5gs and UERANSIM here with all default values.. (should I edit any values?)

I have a 2 nodes K8s deployment with enough resources..

I'm using NFS provider for the PV/PVCs of the MongoDB.. PVC is Bound and consumed by MongoDB..

For some reason, the SCTP connection is not established ..

All Pods are Running and looking healthy..

kg po 
NAME                                              READY   STATUS    RESTARTS      AGE
nfs-subdir-external-provisioner-ff8fdc59b-rvzd9   1/1     Running   0             37m
open5gs-amf-74867f4d79-rgmkm                      1/1     Running   0             31m
open5gs-ausf-6f7b99444d-jp89j                     1/1     Running   0             31m
open5gs-bsf-78cbddcf6d-kstb2                      1/1     Running   0             31m
open5gs-mongodb-76d8dfbbdb-fzzqk                  1/1     Running   0             31m
open5gs-nrf-5f58b84585-wlbs6                      1/1     Running   0             31m
open5gs-nssf-8676d9bc7b-9qj28                     1/1     Running   0             31m
open5gs-pcf-655ff4967f-pvc5g                      1/1     Running   4 (27m ago)   31m
open5gs-populate-578dd7d4d8-sc9zg                 1/1     Running   0             31m
open5gs-smf-7f864d7d99-g4vhc                      1/1     Running   0             31m
open5gs-udm-7cf88b7c58-zmdj5                      1/1     Running   0             31m
open5gs-udr-6c96f5d447-9jkfk                      1/1     Running   5 (28m ago)   31m
open5gs-upf-fcc6fcd5c-tzd8x                       1/1     Running   0             31m
open5gs-webui-567c65bc7b-n566b                    1/1     Running   0             31m
ueransim-gnb-7d8867667f-4d42f                     1/1     Running   0             25m
ueransim-gnb-ues-6487c85db9-5fhcv                 1/1     Running   0             25m

Here are the logs from different CNFs

UE-RANSIM gNB

kubectl logs deployment/ueransim-gnb -f
N2_BIND_IP: 10.0.0.20
N3_BIND_IP: 10.0.0.20
RADIO_BIND_IP: 10.0.0.20
AMF_IP: 10.102.143.93
Launching gnb: nr-gnb -c gnb.yaml
UERANSIM v3.2.6
[2023-01-21 21:32:40.760] [sctp] [info] Trying to establish SCTP connection... (10.102.143.93:38412)
[2023-01-21 21:32:41.236] [rrc] [debug] UE[1] new signal detected
[2023-01-21 21:32:41.240] [rrc] [debug] UE[2] new signal detected
[2023-01-21 21:36:03.518] [sctp] [error] Connecting to 10.102.143.93:38412 failed. SCTP could not connect: Operation timed out

SMF

kubectl logs deployment/open5gs-smf -f
Open5GS daemon v2.4.11

01/21 21:29:13.000: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/smf.yaml' (../lib/app/ogs-init.c:126)
01/21 21:29:13.040: [metrics] INFO: Prometheus mhd_server() [0.0.0.0]:9090 (../lib/metrics/prometheus/context.c:320)
01/21 21:29:13.040: [smf] WARNING: No diameter configuration (../src/smf/fd-path.c:30)
01/21 21:29:13.040: [gtp] INFO: gtp_server() [10.0.1.62]:2123 (../lib/gtp/path.c:30)
01/21 21:29:13.040: [gtp] INFO: gtp_server() [10.0.1.62]:2152 (../lib/gtp/path.c:30)
01/21 21:29:13.040: [pfcp] INFO: pfcp_server() [10.0.1.62]:8805 (../lib/pfcp/path.c:30)
01/21 21:29:13.040: [pfcp] INFO: ogs_pfcp_connect() [10.110.42.201]:8805 (../lib/pfcp/path.c:61)
01/21 21:29:13.041: [sbi] INFO: NF Service [nsmf-pdusession] (../lib/sbi/context.c:1400)
01/21 21:29:13.041: [sbi] INFO: nghttp2_server() [10.0.1.62]:7777 (../lib/sbi/nghttp2-server.c:150)
01/21 21:29:13.042: [app] INFO: SMF initialize...done (../src/smf/app.c:31)
01/21 21:29:20.557: [pfcp] WARNING: [1] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:29:24.044: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:29:24.044: [smf] WARNING: client_cb() failed [-3] (../src/smf/sbi-path.c:55)
01/21 21:29:24.044: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:29:24.045: [sbi] WARNING: [a647a002-99d2-41ed-a156-4373f5fe4ca2] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:29:24.046: [sbi] INFO: [a647a002-99d2-41ed-a156-4373f5fe4ca2] NF registered [Heartbeat:10s] (../lib/sbi/nf-sm.c:222)
01/21 21:29:31.436: [sbi] INFO: [6fdb9438-99d2-41ed-9b16-431c81f1ba2f] (NRF-notify) NF registered (../lib/sbi/nnrf-handler.c:628)
01/21 21:29:31.436: [sbi] INFO: [6fdb9438-99d2-41ed-9b16-431c81f1ba2f] (NRF-notify) NF Profile updated (../lib/sbi/nnrf-handler.c:638)
01/21 21:29:31.553: [pfcp] WARNING: [2] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:29:35.046: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:29:42.558: [pfcp] WARNING: [3] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:29:46.053: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:29:53.557: [pfcp] WARNING: [4] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:29:57.056: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:30:04.563: [pfcp] WARNING: [5] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:30:08.059: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:30:15.579: [pfcp] WARNING: [6] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:30:19.063: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:30:26.577: [pfcp] WARNING: [7] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:30:30.068: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:30:37.580: [pfcp] WARNING: [8] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:30:41.069: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:30:48.577: [pfcp] WARNING: [9] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:30:52.071: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:30:59.578: [pfcp] WARNING: [10] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:31:03.097: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:31:10.647: [pfcp] WARNING: [11] LOCAL  No Reponse. Give up! for step 1 type 5 peer [10.110.42.201]:8805 (../lib/pfcp/xact.c:613)
01/21 21:31:12.837: [pfcp] INFO: ogs_pfcp_connect() [10.0.1.114]:8805 (../lib/pfcp/path.c:61)
01/21 21:31:12.838: [smf] INFO: PFCP associated [10.0.1.114]:8805 (../src/smf/pfcp-sm.c:174)
01/21 21:31:14.108: [smf] WARNING: Retry to association with peer [10.110.42.201]:8805 failed (../src/smf/pfcp-sm.c:107)
01/21 21:31:14.110: [smf] INFO: PFCP associated [10.110.42.201]:8805 (../src/smf/pfcp-sm.c:174)
01/21 21:31:15.171: [sbi] INFO: [ef12ed46-99d2-41ed-97eb-1595bb41cf90] (NRF-notify) NF registered (../lib/sbi/nnrf-handler.c:628)
01/21 21:31:15.172: [sbi] INFO: [ef12ed46-99d2-41ed-97eb-1595bb41cf90] (NRF-notify) NF Profile updated (../lib/sbi/nnrf-handler.c:638)
01/21 21:31:23.840: [pfcp] ERROR: invalid step[0] type[2] (../lib/pfcp/xact.c:432)
01/21 21:31:23.840: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:708)
01/21 21:31:26.343: [pfcp] ERROR: invalid step[0] type[2] (../lib/pfcp/xact.c:432)
01/21 21:31:26.343: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:708)
01/21 21:31:28.876: [pfcp] ERROR: invalid step[0] type[2] (../lib/pfcp/xact.c:432)
01/21 21:31:28.876: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:708)
01/21 21:31:31.376: [pfcp] WARNING: [13] LOCAL  No Reponse. Give up! for step 1 type 1 peer [10.0.1.114]:8805 (../lib/pfcp/xact.c:613)
01/21 21:31:31.376: [smf] WARNING: No Heartbeat from UPF [10.0.1.114]:8805 (../src/smf/pfcp-sm.c:316)
01/21 21:31:31.376: [smf] INFO: PFCP de-associated [10.0.1.114]:8805 (../src/smf/pfcp-sm.c:181)

AMF

kubectl logs deployment/open5gs-amf -f
Open5GS daemon v2.4.11

01/21 21:27:42.971: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/amf.yaml' (../lib/app/ogs-init.c:126)
01/21 21:27:42.983: [metrics] INFO: Prometheus mhd_server() [0.0.0.0]:9090 (../lib/metrics/prometheus/context.c:320)
01/21 21:27:42.984: [sbi] INFO: NF Service [namf-comm] (../lib/sbi/context.c:1400)
01/21 21:27:42.984: [sbi] INFO: nghttp2_server() [10.0.1.206]:7777 (../lib/sbi/nghttp2-server.c:150)
01/21 21:27:43.002: [amf] INFO: ngap_server() [10.0.1.206]:38412 (../src/amf/ngap-sctp.c:61)
01/21 21:27:43.002: [sctp] INFO: AMF initialize...done (../src/amf/app.c:33)
01/21 21:27:53.985: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:27:53.985: [amf] WARNING: client_cb() failed [-3] (../src/amf/sbi-path.c:56)
01/21 21:27:53.985: [sbi] WARNING: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:28:04.997: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:28:04.997: [amf] WARNING: client_cb() failed [-3] (../src/amf/sbi-path.c:56)
01/21 21:28:04.997: [sbi] WARNING: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:28:16.001: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:28:16.001: [amf] WARNING: client_cb() failed [-3] (../src/amf/sbi-path.c:56)
01/21 21:28:16.001: [sbi] WARNING: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:28:27.002: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:28:27.002: [amf] WARNING: client_cb() failed [-3] (../src/amf/sbi-path.c:56)
01/21 21:28:27.002: [sbi] WARNING: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:28:38.002: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:28:38.002: [amf] WARNING: client_cb() failed [-3] (../src/amf/sbi-path.c:56)
01/21 21:28:38.002: [sbi] WARNING: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:28:49.003: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:28:49.003: [amf] WARNING: client_cb() failed [-3] (../src/amf/sbi-path.c:56)
01/21 21:28:49.003: [sbi] WARNING: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:29:00.010: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:29:00.010: [amf] WARNING: client_cb() failed [-3] (../src/amf/sbi-path.c:56)
01/21 21:29:00.010: [sbi] WARNING: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:29:11.012: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:29:11.012: [amf] WARNING: client_cb() failed [-3] (../src/amf/sbi-path.c:56)
01/21 21:29:11.012: [sbi] WARNING: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:29:22.062: [sbi] ERROR: Connection timer expired (../lib/sbi/client.c:495)
01/21 21:29:22.062: [amf] WARNING: client_cb() failed [-3] (../src/amf/sbi-path.c:56)
01/21 21:29:22.063: [sbi] WARNING: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] Retry to registration with NRF (../lib/sbi/nf-sm.c:182)
01/21 21:29:22.065: [sbi] INFO: [709b5c00-99d2-41ed-a70a-c14fd2ad81ed] NF registered [Heartbeat:10s] (../lib/sbi/nf-sm.c:222)
01/21 21:29:22.367: [sbi] INFO: [abd79bc6-99d2-41ed-bb81-b73c88955538] (NRF-notify) NF registered (../lib/sbi/nnrf-handler.c:628)
01/21 21:29:22.367: [sbi] INFO: [abd79bc6-99d2-41ed-bb81-b73c88955538] (NRF-notify) NF Profile updated (../lib/sbi/nnrf-handler.c:638)
01/21 21:29:24.046: [sbi] INFO: [a647a002-99d2-41ed-a156-4373f5fe4ca2] (NRF-notify) NF registered (../lib/sbi/nnrf-handler.c:628)
01/21 21:29:24.046: [sbi] INFO: [a647a002-99d2-41ed-a156-4373f5fe4ca2] (NRF-notify) NF Profile updated (../lib/sbi/nnrf-handler.c:638)
01/21 21:29:31.326: [sbi] INFO: [aa9e70fe-99d2-41ed-a9a7-c532f02dcd23] (NRF-notify) NF registered (../lib/sbi/nnrf-handler.c:628)
01/21 21:29:31.326: [sbi] INFO: [aa9e70fe-99d2-41ed-a9a7-c532f02dcd23] (NRF-notify) NF Profile updated (../lib/sbi/nnrf-handler.c:638)
01/21 21:29:31.434: [sbi] INFO: [6fdb9438-99d2-41ed-9b16-431c81f1ba2f] (NRF-notify) NF registered (../lib/sbi/nnrf-handler.c:628)
01/21 21:29:31.434: [sbi] INFO: [6fdb9438-99d2-41ed-9b16-431c81f1ba2f] (NRF-notify) NF Profile updated (../lib/sbi/nnrf-handler.c:638)
01/21 21:29:31.435: [sbi] WARNING: [6fdb9438-99d2-41ed-9b16-431c81f1ba2f] (NRF-notify) NF has already been added (../lib/sbi/nnrf-handler.c:632)
01/21 21:29:31.435: [sbi] INFO: [6fdb9438-99d2-41ed-9b16-431c81f1ba2f] (NRF-notify) NF Profile updated (../lib/sbi/nnrf-handler.c:638)
01/21 21:29:31.435: [sbi] WARNING: NF EndPoint updated [10.0.0.117:80] (../lib/sbi/context.c:1572)
01/21 21:29:31.435: [sbi] WARNING: NF EndPoint updated [10.0.0.117:7777] (../lib/sbi/context.c:1481)
01/21 21:31:15.170: [sbi] INFO: [ef12ed46-99d2-41ed-97eb-1595bb41cf90] (NRF-notify) NF registered (../lib/sbi/nnrf-handler.c:628)
01/21 21:31:15.170: [sbi] INFO: [ef12ed46-99d2-41ed-97eb-1595bb41cf90] (NRF-notify) NF Profile updated (../lib/sbi/nnrf-handler.c:638)

Also, I cant see the uesimtun0 and uesimtun1 interfaces

kubectl exec deployment/ueransim-gnb-ues -ti -- bash

bash-5.1# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
33: eth0@if34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3a:6e:b0:fb:88:93 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet 10.0.1.121/32 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::386e:b0ff:fefb:8893/64 scope link 
       valid_lft forever preferred_lft forever

Logs from the ueransim-gnb-ues-6487c85db9-5fhcv Pod

k logs ueransim-gnb-ues-6487c85db9-5fhcv
GNB_IP: 10.0.0.20
Launching ue: nr-ue -c ue.yaml
UERANSIM v3.2.6
[2023-01-21 21:32:40.898] [999700000000002|nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2023-01-21 21:32:40.899] [999700000000001|nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2023-01-21 21:32:40.900] [999700000000001|rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2023-01-21 21:32:40.902] [999700000000002|rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2023-01-21 21:32:40.905] [999700000000001|nas] [info] Selected plmn[999/70]
[2023-01-21 21:32:40.905] [999700000000001|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
[2023-01-21 21:32:40.906] [999700000000001|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
[2023-01-21 21:32:40.906] [999700000000001|rrc] [error] Cell selection failure, no suitable or acceptable cell found
[2023-01-21 21:32:40.906] [999700000000002|nas] [info] Selected plmn[999/70]
[2023-01-21 21:32:40.907] [999700000000002|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
[2023-01-21 21:32:40.907] [999700000000002|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
[2023-01-21 21:32:40.907] [999700000000002|rrc] [error] Cell selection failure, no suitable or acceptable cell found
[2023-01-21 21:32:46.409] [999700000000001|nas] [info] UE switches to state [MM-DEREGISTERED/NO-CELL-AVAILABLE]
[2023-01-21 21:32:46.409] [999700000000002|nas] [info] UE switches to state [MM-DEREGISTERED/NO-CELL-AVAILABLE]
[2023-01-21 21:33:10.941] [999700000000001|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
[2023-01-21 21:33:10.941] [999700000000001|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
[2023-01-21 21:33:10.941] [999700000000001|rrc] [error] Cell selection failure, no suitable or acceptable cell found

Questions about open5gs charts

Thanks for the well organized repo.

I deployed the Open5gs and UERANSIM, and I had some questions while doing so:

Related to Open5gs:

Why the MME, HSS, SGWC and SGWU are enabled by default in the open5gs values chart? shouldnt only the 5G CNFs be enabled by default or are you targeting "Combo Dual" core with this ?
Why using StatefulSets for AMF, NRF, SMF ,, etc ? why not Deployment since there is no state to be preserved here. or am I missing something ?

Related to UERANSIM:

In the openverso-charts/charts/ueransim/values.yaml file, there is this value (amf: open5gs-amf ). Where exactly it is being used? I didnt know what does it mean..
How this deployment is dealing with the TUN interface?
Is'nt Multus a must in this situation?
In the charts/ueransim/resources/gnb.yaml there is a variable called AMF_ADDR. Is this the IP address of the AMF Pod that we should set manually ?
These 3 IPs in the charts/ueransim/resources/gnb.yaml

linkIp: 127.0.0.1
ngapIp: 127.0.0.1 
gtpIp: 127.0.0.1

Should be left like that? if not, how else to define an IP for the gnodeb container running within a Pod next to the ue container?

In the openverso-charts/charts/ueransim/resources/ue.yaml, should this be left without changes?

# List of gNB IP addresses for Radio Link Simulation
gnbSearchList:
  - 127.0.0.1

Sorry for the long lquestionare but since I want to do heavy testing on K8s/5G deployment, I wanted to understand such details..

Thanks in advance..

BR
SAM

Exposing the AMF outside the cluster for external access

Hello,
Thanks for the great work here!

This is not a issue but a question related to exposing the AMF outside the cluster for external access.
What is the best way to do that and how to do it? (.yaml)

Thanks.

GNB_IP is set to null leading to UERANSIM UE crash while deploying

In the Values.yaml, there is no option to set the GNB_IP and this value is set to NULL and deployment of UE crashes with below error

GNB_IP:
Launching ue: nr-ue -c ue.yaml
UERANSIM v3.2.6
terminate called after throwing an instance of 'LibError'
what(): Bad Inet address: null Invalid argument
/entrypoint.sh: line 41: 15 Aborted (core dumped) nr-ue -c ue.yaml $@

As a workaround, if the GNB_IP is manually editted on the configMap and then restarting the POD makes it work, setting up the GNB_IP needs to be allowed in the values.yaml file, it is currently missing...

https://github.com/Gradiant/openverso-charts/blob/master/charts/ueransim-gnb/values.yaml

ues:
enabled: false
count: 1
initialMSISDN: '0000000001'
key: 465B5CE8B199B49FAA5F0A2EE238A6BC
op: E8ED289DEBA952E4283B54E88E6183CA
opType: OPC
apnList:
- type: 'IPv4'
apn: 'internet'
slice:
sst: 1
sd: "0x111111"
emergency: false
resources:
limits: {}
requests: {}
podSecurityContext:
enabled: false
containerSecurityContext:
enabled: false
podLabels: {}
podAnnotations: {}
affinity: {}
nodeSelector: {}
tolerations: []

AMF & MME do not start

Hi,

Congrats for such a nice project!

I was able to run the source code of ope5gs and an old version of openverso-charts too, I believe it was the 18fa3e7, but unfortunately I do not have the version anymore. I am trying to run the latest tgz and I am getting an error while trying to set the AMF/MME up. Seems like an SCTP error, do you know what am I doing wrong?

Below the logs:

root@master-node:/home/ims/openverso-charts/charts# kubectl logs open5gs-0-1627657923-open5gs-amf-0
Open5GS daemon v2.0.18

07/30 15:14:07.457: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/amf.yaml' (../src/main.c:54)
07/30 15:14:07.462: [app] INFO: AMF initialize...done (../src/amf/app.c:33)
07/30 15:14:07.463: [sbi] INFO: sbi_server() [10.244.0.80]:7777 (../lib/sbi/server.c:298)
07/30 15:14:07.463: [sock] ERROR: setsockopt for SCTP_PEER_ADDR_PARAMS failed (22:Invalid argument) (../lib/sctp/ogs-lksctp.c:296)
07/30 15:14:07.463: [sock] FATAL: ogs_sctp_socket: Assertion `rv == OGS_OK' failed. (../lib/sctp/ogs-lksctp.c:63)
07/30 15:14:07.463: [core] FATAL: backtrace() returned 11 addresses (../lib/core/ogs-abort.c:37)
/usr/local/lib/x86_64-linux-gnu/libogssctp.so.2(ogs_sctp_socket+0x210) [0x7f7c23e2e976]
/usr/local/lib/x86_64-linux-gnu/libogssctp.so.2(ogs_sctp_server+0x11e) [0x7f7c23e2ec37]
open5gs-amfd(+0x130de) [0x55e97290a0de]
open5gs-amfd(+0x2f54c) [0x55e97292654c]
open5gs-amfd(+0x19c71) [0x55e972910c71]
/usr/local/lib/x86_64-linux-gnu/libogscore.so.2(ogs_fsm_init+0x9a) [0x7f7c23e540ef]
open5gs-amfd(+0x5aea) [0x55e9728fcaea]
/usr/local/lib/x86_64-linux-gnu/libogscore.so.2(+0x131ee) [0x7f7c23e471ee]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7f7c23ab5fa3]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f7c239e44cf]

The services:

root@master-node:/home/ims/openverso-charts/charts# kubectl get services
NAME                                 TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                                AGE
kubernetes                           ClusterIP   10.96.0.1        <none>        443/TCP                                18d
open5gs-0-1627657923-mongodb         ClusterIP   10.100.14.222    <none>        27017/TCP                              9m18s
open5gs-0-1627657923-open5gs-amf     ClusterIP   10.103.28.147    <none>        7777/TCP,38412/UDP                     9m18s
open5gs-0-1627657923-open5gs-ausf    ClusterIP   10.111.63.215    <none>        7777/TCP                               9m18s
open5gs-0-1627657923-open5gs-hss     ClusterIP   10.111.172.220   <none>        3868/TCP                               9m18s
open5gs-0-1627657923-open5gs-mme     ClusterIP   10.98.83.247     <none>        36412/SCTP,3868/SCTP,2123/UDP          9m18s
open5gs-0-1627657923-open5gs-nrf     ClusterIP   10.111.179.43    <none>        7777/TCP                               9m18s
open5gs-0-1627657923-open5gs-pcrf    ClusterIP   10.106.143.9     <none>        3868/SCTP                              9m18s
open5gs-0-1627657923-open5gs-sgwc    ClusterIP   10.103.119.77    <none>        2123/UDP,8805/UDP                      9m18s
open5gs-0-1627657923-open5gs-sgwu    ClusterIP   10.102.145.26    <none>        2152/UDP,8805/UDP                      9m18s
open5gs-0-1627657923-open5gs-smf     ClusterIP   10.103.93.177    <none>        2123/UDP,8805/UDP,3868/SCTP,7777/TCP   9m18s
open5gs-0-1627657923-open5gs-udm     ClusterIP   10.96.139.56     <none>        7777/TCP                               9m18s
open5gs-0-1627657923-open5gs-udr     ClusterIP   10.107.220.239   <none>        7777/TCP                               9m18s
open5gs-0-1627657923-open5gs-upf     ClusterIP   10.105.250.8     <none>        2152/UDP,8805/UDP                      9m18s
open5gs-0-1627657923-open5gs-webui   ClusterIP   10.105.146.116   <none>        3000/TCP                               9m18s

The describe:

root@master-node:/home/ims/openverso-charts/charts# kubectl describe pods open5gs-0-1627657923-open5gs-amf
Name:         open5gs-0-1627657923-open5gs-amf-0
Namespace:    default
Priority:     0
Node:         master-node/10.221.194.166
Start Time:   Fri, 30 Jul 2021 12:12:07 -0300
Labels:       app.kubernetes.io/component=amf
              app.kubernetes.io/instance=open5gs-0-1627657923
              app.kubernetes.io/name=open5gs
              controller-revision-hash=open5gs-0-1627657923-open5gs-amf-696b4699d4
              statefulset.kubernetes.io/pod-name=open5gs-0-1627657923-open5gs-amf-0
Annotations:  <none>
Status:       Running
IP:           10.244.0.80
IPs:
  IP:           10.244.0.80
Controlled By:  StatefulSet/open5gs-0-1627657923-open5gs-amf
Containers:
  amf:
    Container ID:  docker://d00ef224a353eb5de3ddab0274aacbc4a0af18f762f04dc10aa9a7a05623c7b1
    Image:         docker.io/openverso/open5gs:2.0.18
    Image ID:      docker-pullable://openverso/open5gs@sha256:ecffc96da540e5c7209b845a00ca818826dda6053c618cf82313391c794bc19b
    Ports:         7777/TCP, 38412/UDP
    Host Ports:    0/TCP, 0/UDP
    Command:
      open5gs-amfd
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    139
      Started:      Fri, 30 Jul 2021 12:18:27 -0300
      Finished:     Fri, 30 Jul 2021 12:18:27 -0300
    Ready:          False
    Restart Count:  6
    Environment:    <none>
    Mounts:
      /opt/open5gs/etc/open5gs/amf.yaml from amf-config (rw,path="amf.yaml")
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-xcrnx (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             False 
  ContainersReady   False 
  PodScheduled      True 
Volumes:
  amf-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      open5gs-0-1627657923-open5gs-amf
    Optional:  false
  kube-api-access-xcrnx:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                  From               Message
  ----     ------     ----                 ----               -------
  Normal   Scheduled  10m                  default-scheduler  Successfully assigned default/open5gs-0-1627657923-open5gs-amf-0 to master-node
  Normal   Pulled     10m                  kubelet            Successfully pulled image "docker.io/openverso/open5gs:2.0.18" in 5.713116547s
  Normal   Pulled     10m                  kubelet            Successfully pulled image "docker.io/openverso/open5gs:2.0.18" in 16.485986027s
  Normal   Pulled     9m51s                kubelet            Successfully pulled image "docker.io/openverso/open5gs:2.0.18" in 1.606681301s
  Normal   Created    9m21s (x4 over 10m)  kubelet            Created container amf
  Normal   Started    9m21s (x4 over 10m)  kubelet            Started container amf
  Normal   Pulled     9m21s                kubelet            Successfully pulled image "docker.io/openverso/open5gs:2.0.18" in 1.780448005s
  Normal   Pulling    8m38s (x5 over 10m)  kubelet            Pulling image "docker.io/openverso/open5gs:2.0.18"
  Normal   Pulled     8m36s                kubelet            Successfully pulled image "docker.io/openverso/open5gs:2.0.18" in 1.741149834s
  Warning  BackOff    19s (x47 over 10m)   kubelet            Back-off restarting failed container

The pods:

root@master-node:/home/ims/openverso-charts/charts# kubectl get pods
NAME                                                  READY   STATUS             RESTARTS   AGE
open5gs-0-1627657923-mongodb-548b8b9688-4dh7w         1/1     Running            0          11m
open5gs-0-1627657923-open5gs-amf-0                    0/1     CrashLoopBackOff   6          11m
open5gs-0-1627657923-open5gs-ausf-0                   1/1     Running            0          11m
open5gs-0-1627657923-open5gs-hss-0                    1/1     Running            1          11m
open5gs-0-1627657923-open5gs-mme-0                    0/1     CrashLoopBackOff   6          11m
open5gs-0-1627657923-open5gs-nrf-0                    1/1     Running            0          11m
open5gs-0-1627657923-open5gs-pcrf-0                   1/1     Running            1          11m
open5gs-0-1627657923-open5gs-sgwc-0                   1/1     Running            0          11m
open5gs-0-1627657923-open5gs-sgwu-0                   1/1     Running            0          11m
open5gs-0-1627657923-open5gs-smf-0                    1/1     Running            0          11m
open5gs-0-1627657923-open5gs-udm-0                    1/1     Running            0          11m
open5gs-0-1627657923-open5gs-udr-0                    1/1     Running            0          11m
open5gs-0-1627657923-open5gs-upf-0                    1/1     Running            0          11m
open5gs-0-1627657923-open5gs-webui-56d54b586b-9df2n   1/1     Running            1          11m

Thank you in advance!

Issue in deploying openverso/oai-gnb helm chart with USRP B210

I am trying to setup Open5GS and OAI-GNodeB following the tutorial at: https://gradiant.github.io/openverso-charts/open5gs-oaignb.html . I have deployed a kubernetes cluster and to one of the nodes I have connected a USRP B210. Now I execute "helm install oai-gnb openverso/oai-gnb --version 0.3.1 --values https://gradiant.github.io/openverso-charts/docs/open5gs-oaignb/gnb-values.yaml " at the kubernetes cluster. But the oai-gnb-0 pod is in Pending state.

The output of "kubectl describe pods oai-gnb-0" shows FailedScheduling with the following message:

"0/3 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }, 3 Insufficient ettus.com/usrp. preemption: 0/3 nodes are available: 1 Preemption is not helpful for scheduling, 2 No preemption victims found for incoming pod."

Please let me know what may be the issue here. Please note that I have checked that the USRP is connected to the worker node (using "sudo uhd_usrp_probe" command). @cgiraldo

[sctp] [error]: could not connect: Connection timed out

AMF:

Open5GS daemon v2.4.4
04/01 02:32:02.459: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/amf.yaml' (../lib/app/ogs-init.c:129)
04/01 02:32:02.465: [sbi] INFO: nghttp2_server() [10.42.3.198]:7777 (../lib/sbi/nghttp2-server.c:144)
04/01 02:32:02.465: [amf] INFO: ngap_server() [10.42.3.198]:38412 (../src/amf/ngap-sctp.c:53)
04/01 02:32:02.465: [sctp] INFO: AMF initialize...done (../src/amf/app.c:33)
04/01 02:32:02.479: [amf] INFO: [e9d5a290-b163-41ec-891e-1d07012218e8] NF registred [Heartbeat:10s] (../src/amf/nf-sm.c:198)

GNB:

Fri, Apr 1 2022 3:48:54 am | Launching gnb: nr-gnb -c gnb.yaml
Fri, Apr 1 2022 3:48:54 am | UERANSIM v3.2.6
Fri, Apr 1 2022 3:48:54 am | [2022-04-01 02:48:54.094] [sctp] [info] Trying to establish SCTP connection... (10.43.211.197:38412)
Fri, Apr 1 2022 3:49:46 am | [2022-04-01 02:49:46.149] [rrc] [debug] UE[1] new signal detected
Fri, Apr 1 2022 3:49:46 am | [2022-04-01 02:49:46.150] [rrc] [debug] UE[2] new signal detected
Fri, Apr 1 2022 3:49:46 am | [2022-04-01 02:49:46.153] [rrc] [debug] UE[3] new signal detected
Fri, Apr 1 2022 3:49:46 am | [2022-04-01 02:49:46.154] [rrc] [debug] UE[4] new signal detected
[2022-04-01 02:53:58.174] [sctp] [error] Connecting to 10.43.211.197:38412 failed. SCTP could not connect: Connection timed out

UE:

[2022-04-01 02:53:46.242] [999700000000001\|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
Fri, Apr 1 2022 3:53:46 am | [2022-04-01 02:53:46.242] [999700000000001\|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
Fri, Apr 1 2022 3:53:46 am | [2022-04-01 02:53:46.242] [999700000000001\|rrc] [error] Cell selection failure, no suitable or acceptable cell found

NRF:


Open5GS daemon v2.4.4
04/01 03:02:02.827: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/nrf.yaml' (../lib/app/ogs-init.c:129)
04/01 03:02:02.844: [sbi] INFO: nghttp2_server() [10.42.4.5]:7777 (../lib/sbi/nghttp2-server.c:144)
04/01 03:02:02.844: [app] INFO: NRF initialize...done (../src/nrf/app.c:31)
04/01 03:02:03.056: [nrf] WARNING: Not found [caff84dc-b161-41ec-98f1-2395a2a55df4] (../src/nrf/nrf-sm.c:114)
04/01 03:02:03.358: [nrf] INFO: [caff84dc-b161-41ec-98f1-2395a2a55df4] NF registred [Heartbeat:10s] (../src/nrf/nf-sm.c:192)
04/01 03:02:03.745: [nrf] WARNING: Not found [e9d5a290-b163-41ec-891e-1d07012218e8] (../src/nrf/nrf-sm.c:114)
04/01 03:02:03.745: [nrf] INFO: [e9d5a290-b163-41ec-891e-1d07012218e8] NF registred [Heartbeat:10s] (../src/nrf/nf-sm.c:192)
04/01 03:02:04.952: [nrf] WARNING: Not found [ba085014-b161-41ec-8e81-85c475af1f96] (../src/nrf/nrf-sm.c:114)
04/01 03:02:05.253: [nrf] INFO: [ba085014-b161-41ec-8e81-85c475af1f96] NF registred [Heartbeat:10s] (../src/nrf/nf-sm.c:192)
04/01 03:02:06.152: [nrf] WARNING: Not found [c74e2082-b161-41ec-accd-b1c5b448e825] (../src/nrf/nrf-sm.c:114)
04/01 03:02:06.299: [nrf] WARNING: Not found [c77efcc0-b161-41ec-af6d-0132c4585684] (../src/nrf/nrf-sm.c:114)
04/01 03:02:06.454: [nrf] INFO: [c74e2082-b161-41ec-accd-b1c5b448e825] NF registred [Heartbeat:10s] (../src/nrf/nf-sm.c:192)
04/01 03:02:06.601: [nrf] INFO: [c77efcc0-b161-41ec-af6d-0132c4585684] NF registred [Heartbeat:10s] (../src/nrf/nf-sm.c:192)
04/01 03:02:08.123: [nrf] WARNING: Not found [c893b63c-b161-41ec-83af-0b9107aec08d] (../src/nrf/nrf-sm.c:114)
04/01 03:02:08.182: [nrf] WARNING: Not found [c235093a-b161-41ec-bd17-917494b58f85] (../src/nrf/nrf-sm.c:114)
04/01 03:02:08.424: [nrf] INFO: [c893b63c-b161-41ec-83af-0b9107aec08d] NF registred [Heartbeat:10s] (../src/nrf/nf-sm.c:192)
04/01 03:02:08.484: [nrf] INFO: [c235093a-b161-41ec-bd17-917494b58f85] NF registred [Heartbeat:10s] (../src/nrf/nf-sm.c:192)
04/01 03:02:10.553: [nrf] WARNING: Not found [c9f7ae52-b161-41ec-b141-7df1713d15a4] (../src/nrf/nrf-sm.c:114)
04/01 03:02:10.855: [nrf] INFO: [c9f7ae52-b161-41ec-b141-7df1713d15a4] NF registred [Heartbeat:10s] (../src/nrf/nf-sm.c:192)

UPF:


Creating ogstun device
net.ipv6.conf.all.disable_ipv6 = 0
Open5GS daemon v2.4.4
04/01 03:08:33.859: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/upf.yaml' (../lib/app/ogs-init.c:129)
04/01 03:08:33.876: [pfcp] INFO: pfcp_server() [10.42.3.57]:8805 (../lib/pfcp/path.c:30)
04/01 03:08:33.876: [pfcp] INFO: ogs_pfcp_connect() [10.43.62.51]:8805 (../lib/pfcp/path.c:59)
04/01 03:08:33.876: [gtp] INFO: gtp_server() [10.42.3.57]:2152 (../lib/gtp/path.c:30)
04/01 03:08:33.877: [app] INFO: UPF initialize...done (../src/upf/app.c:31)
04/01 03:08:33.877: [pfcp] INFO: ogs_pfcp_connect() [10.42.4.232]:8805 (../lib/pfcp/path.c:59)
04/01 03:08:33.877: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:08:33.877: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:08:36.378: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:08:36.378: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:08:38.880: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:08:38.880: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:08:41.381: [pfcp] WARNING: [1] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:08:44.877: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:08:44.878: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:08:44.878: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:08:44.878: [upf] WARNING: cannot handle PFCP message type[1] (../src/upf/pfcp-sm.c:139)
04/01 03:08:47.380: [pfcp] WARNING: [2] REMOTE Request Duplicated. Discard! for step 1 type 1 peer [10.42.4.232]:8805 (../lib/pfcp/xact.c:409)
04/01 03:08:47.380: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:08:47.380: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:08:49.881: [pfcp] WARNING: [2] REMOTE Request Duplicated. Discard! for step 1 type 1 peer [10.42.4.232]:8805 (../lib/pfcp/xact.c:409)
04/01 03:08:49.882: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:08:49.882: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:08:52.382: [pfcp] WARNING: [2] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:08:52.382: [upf] INFO: PFCP associated (../src/upf/pfcp-sm.c:173)
04/01 03:08:55.882: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:08:55.882: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:08:55.882: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:08:58.385: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:08:58.385: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:00.886: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:00.886: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:03.387: [pfcp] WARNING: [3] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:09:06.885: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:09:06.886: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:06.886: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:09.387: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:09.387: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:11.889: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:11.889: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:14.388: [pfcp] WARNING: [5] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:09:17.889: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:09:17.890: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:17.890: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:20.392: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:20.392: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:22.895: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:22.895: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:25.395: [pfcp] WARNING: [7] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:09:28.893: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:09:28.894: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:28.894: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:31.465: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:31.465: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:33.898: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:33.898: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:36.398: [pfcp] WARNING: [9] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:09:39.896: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:09:39.897: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:39.897: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:42.400: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:42.400: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:44.902: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:44.902: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:47.402: [pfcp] WARNING: [11] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:09:50.901: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:09:50.902: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:50.902: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:53.403: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:53.403: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:55.904: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:09:55.904: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:09:58.404: [pfcp] WARNING: [13] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:10:01.902: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:10:01.903: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:01.903: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:04.406: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:04.406: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:06.908: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:06.908: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:09.408: [pfcp] WARNING: [15] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:10:12.905: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:10:12.906: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:12.906: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:15.413: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:15.413: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:17.910: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:17.910: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:20.410: [pfcp] WARNING: [17] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:10:23.910: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:10:23.910: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:23.910: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:26.413: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:26.413: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:28.914: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:28.914: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:31.414: [pfcp] WARNING: [19] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:10:34.913: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:10:34.914: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:34.914: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:37.417: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:37.417: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:39.918: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:39.918: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:42.418: [pfcp] WARNING: [21] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:10:45.917: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:10:45.918: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:45.918: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:48.419: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:48.419: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:50.920: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:50.920: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:53.420: [pfcp] WARNING: [23] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:10:56.918: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:10:56.919: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:56.919: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:10:59.422: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:10:59.422: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:01.923: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:01.923: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:04.423: [pfcp] WARNING: [25] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:11:07.921: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:11:07.922: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:07.922: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:10.425: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:10.425: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:12.926: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:12.927: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:15.427: [pfcp] WARNING: [27] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:11:18.925: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:11:18.926: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:18.926: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:21.429: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:21.429: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:23.931: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:23.931: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:26.430: [pfcp] WARNING: [29] LOCAL No Reponse. Give up! for step 1 type 5 peer [10.43.62.51]:8805 (../lib/pfcp/xact.c:618)
04/01 03:11:29.929: [upf] WARNING: Retry to association with peer [10.43.62.51]:8805 failed (../src/upf/pfcp-sm.c:106)
04/01 03:11:29.930: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:29.930: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:32.433: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:32.433: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)
04/01 03:11:34.934: [pfcp] ERROR: invalid step[0] type[6] (../lib/pfcp/xact.c:439)
04/01 03:11:34.934: [pfcp] ERROR: ogs_pfcp_xact_update_rx() failed (../lib/pfcp/xact.c:713)

So i deployed open5gs
then subscribe in webui to 999700000000001 - 999700000000004
at last deployed ueransim.
I have tried to ping from gnb to amf and it didn't work to this ping 10.43.211.197.
I'm using cillium in a rke2 cluster.

Restore data in open5gs/mongodb problem using chart open5gs

Hey so i find another problem with restoring data from a persistence volume, first i created a persistence volume, then i change the deployment of open5gs/mongodb storage to /mnt/bitnami/mongodb and finally i tested database with open5gs web ui. When i delete the mongodb pod it should restore the data from the persistence volume and that doesn't happen.

open5gs chart on a commercial gNB

Hi,

I have installed the newest chart for open5gs and inserted the info of mongo db. However, the answer that I get after trying an authentication with a real user is that the supi is not found on the db. Can someone help me understand what is going on? I have tested same config on a non containerized Open5gs and the core works fine.

Below the db output:

> use open5gs
switched to db open5gs
> db.subscribers.find()
{ "_id" : ObjectId("61043fff47479900010acf0a"), "imsi" : "724020000000006", "subscribed_rau_tau_timer" : 12, "network_access_mode" : 2, "subscriber_status" : 0, "access_restriction_data" : 32, "slice" : [ { "sst" : 1, "default_indicator" : true, "_id" : ObjectId("61043fff47479900010acf0b"), "session" : [ { "name" : "internet", "type" : 1, "_id" : ObjectId("61043fff47479900010acf0c"), "pcc_rule" : [ ], "ambr" : { "uplink" : { "value" : 1, "unit" : 3 }, "downlink" : { "value" : 1, "unit" : 3 } }, "qos" : { "index" : 9, "arp" : { "priority_level" : 8, "pre_emption_capability" : 1, "pre_emption_vulnerability" : 1 } } } ] } ], "ambr" : { "uplink" : { "value" : 1, "unit" : 3 }, "downlink" : { "value" : 1, "unit" : 3 } }, "security" : { "k" : "30303030303030303030303030303030", "amf" : "8000", "op" : null, "opc" : "30303030303030303030303030303030" }, "schema_version" : 1, "__v" : 0 }
{ "_id" : ObjectId("6104406047479900010acf0d"), "imsi" : "724020000000005", "subscribed_rau_tau_timer" : 12, "network_access_mode" : 2, "subscriber_status" : 0, "access_restriction_data" : 32, "slice" : [ { "sst" : 1, "default_indicator" : true, "_id" : ObjectId("6104406047479900010acf0e"), "sd" : "D143A5", "session" : [ { "name" : "internet", "type" : 1, "_id" : ObjectId("6104406047479900010acf0f"), "pcc_rule" : [ ], "ambr" : { "uplink" : { "value" : 1, "unit" : 3 }, "downlink" : { "value" : 1, "unit" : 3 } }, "qos" : { "index" : 9, "arp" : { "priority_level" : 8, "pre_emption_capability" : 1, "pre_emption_vulnerability" : 1 } } } ] } ], "ambr" : { "uplink" : { "value" : 1, "unit" : 3 }, "downlink" : { "value" : 1, "unit" : 3 } }, "security" : { "k" : "30303030303030303030303030303030", "amf" : "8000", "op" : null, "opc" : "30303030303030303030303030303030" }, "schema_version" : 1, "__v" : 0 }

All the pods are running fine:

root@master-node:/home/ims/Downloads/open5gs-0.2.1# kubectl get pods -o wide
NAME                                            READY   STATUS    RESTARTS   AGE   IP             NODE          NOMINATED NODE   READINESS GATES
open5gs-0-1627684304-amf-0                      1/1     Running   0          76m   10.244.0.206   master-node   <none>           <none>
open5gs-0-1627684304-ausf-0                     1/1     Running   0          76m   10.244.0.216   master-node   <none>           <none>
open5gs-0-1627684304-hss-0                      1/1     Running   2          76m   10.244.0.213   master-node   <none>           <none>
open5gs-0-1627684304-mme-0                      1/1     Running   0          76m   10.244.0.212   master-node   <none>           <none>
open5gs-0-1627684304-mongodb-6457499d94-sqmsq   1/1     Running   0          76m   10.244.0.201   master-node   <none>           <none>
open5gs-0-1627684304-nrf-0                      1/1     Running   0          76m   10.244.0.202   master-node   <none>           <none>
open5gs-0-1627684304-nssf-0                     1/1     Running   0          76m   10.244.0.203   master-node   <none>           <none>
open5gs-0-1627684304-pcf-0                      1/1     Running   2          76m   10.244.0.204   master-node   <none>           <none>
open5gs-0-1627684304-pcrf-0                     1/1     Running   2          76m   10.244.0.211   master-node   <none>           <none>
open5gs-0-1627684304-sgwc-0                     1/1     Running   0          76m   10.244.0.208   master-node   <none>           <none>
open5gs-0-1627684304-sgwu-0                     1/1     Running   0          76m   10.244.0.205   master-node   <none>           <none>
open5gs-0-1627684304-smf-0                      1/1     Running   0          76m   10.244.0.215   master-node   <none>           <none>
open5gs-0-1627684304-udm-0                      1/1     Running   0          76m   10.244.0.207   master-node   <none>           <none>
open5gs-0-1627684304-udr-0                      1/1     Running   2          76m   10.244.0.210   master-node   <none>           <none>
open5gs-0-1627684304-upf-0                      1/1     Running   0          76m   10.244.0.214   master-node   <none>           <none>
open5gs-0-1627684304-webui-67f5857ff5-gjsmv     1/1     Running   1          76m   10.244.0.209   master-node   <none>           <none>

Services are exposed:

root@master-node:/home/ims/Downloads/open5gs-0.2.1# kubectl get services
NAME                           TYPE        CLUSTER-IP       EXTERNAL-IP      PORT(S)                                AGE
kubernetes                     ClusterIP   10.96.0.1        <none>           443/TCP                                18d
open5gs-0-1627684304-amf       ClusterIP   10.106.30.201    10.221.194.166   7777/TCP,38412/SCTP                    55m
open5gs-0-1627684304-ausf      ClusterIP   10.109.253.231   <none>           7777/TCP                               55m
open5gs-0-1627684304-hss       ClusterIP   10.99.126.140    <none>           3868/SCTP                              55m
open5gs-0-1627684304-mme       ClusterIP   10.100.68.47     <none>           36412/SCTP,3868/SCTP,2123/UDP          55m
open5gs-0-1627684304-mongodb   ClusterIP   10.97.112.162    <none>           27017/TCP                              55m
open5gs-0-1627684304-nrf       ClusterIP   10.102.237.200   <none>           7777/TCP                               55m
open5gs-0-1627684304-nssf      ClusterIP   10.111.24.170    <none>           7777/TCP                               55m
open5gs-0-1627684304-pcf       ClusterIP   10.104.242.38    <none>           7777/TCP                               55m
open5gs-0-1627684304-pcrf      ClusterIP   10.100.47.113    <none>           3868/SCTP                              55m
open5gs-0-1627684304-sgwc      ClusterIP   10.100.12.174    <none>           2123/UDP,8805/UDP                      55m
open5gs-0-1627684304-sgwu      ClusterIP   10.109.151.211   <none>           2152/UDP,8805/UDP                      55m
open5gs-0-1627684304-smf       ClusterIP   10.103.245.64    <none>           2123/UDP,8805/UDP,3868/SCTP,7777/TCP   55m
open5gs-0-1627684304-udm       ClusterIP   10.99.193.34     <none>           7777/TCP                               55m
open5gs-0-1627684304-udr       ClusterIP   10.97.172.30     <none>           7777/TCP                               55m
open5gs-0-1627684304-upf       ClusterIP   10.96.11.93      10.221.194.166   2152/UDP,8805/UDP                      55m
open5gs-0-1627684304-webui     ClusterIP   10.106.207.21    <none>           3000/TCP                               55m

AMF logs:

07/30 22:50:52.678: [amf] INFO: [Added] Number of gNBs is now 1 (../src/amf/context.c:866)
07/30 22:53:38.400: [amf] INFO: InitialUEMessage (../src/amf/ngap-handler.c:349)
07/30 22:53:38.400: [amf] INFO: [Added] Number of gNB-UEs is now 1 (../src/amf/context.c:1829)
07/30 22:53:38.400: [amf] INFO:     RAN_UE_NGAP_ID[0] AMF_UE_NGAP_ID[1] TAC[8101] CellID[0x35b68001] (../src/amf/ngap-handler.c:483)
07/30 22:53:38.400: [amf] INFO: [suci-0-724-03-0000-0-0-0000000005] Unknown UE by SUCI (../src/amf/context.c:1302)
07/30 22:53:38.400: [amf] INFO: [Added] Number of AMF-UEs is now 1 (../src/amf/context.c:1120)
07/30 22:53:38.400: [gmm] INFO: Registration request (../src/amf/gmm-sm.c:131)
07/30 22:53:38.400: [gmm] INFO: [suci-0-724-03-0000-0-0-0000000005]    SUCI (../src/amf/gmm-handler.c:72)
07/30 22:53:38.400: [app] WARNING: Try to discover [AUSF] (../lib/sbi/path.c:109)
07/30 22:53:38.401: [amf] INFO: [f1fd3b0c-f185-41eb-99d2-4153d59bb01d] (NF-discover) NF registered (../src/amf/nnrf-handler.c:332)
07/30 22:53:38.401: [amf] INFO: [f1fd3b0c-f185-41eb-99d2-4153d59bb01d] (NF-discover) NF Profile updated (../src/amf/nnrf-handler.c:391)
07/30 22:53:38.405: [gmm] WARNING: [suci-0-724-03-0000-0-0-0000000005] Cannot find SUCI [404] (../src/amf/gmm-sm.c:527)
07/30 22:53:38.405: [amf] WARNING: [suci-0-724-03-0000-0-0-0000000005] Registration reject [7] (../src/amf/nas-path.c:139)
07/30 22:53:38.408: [amf] INFO: UE Context Release [Action:3] (../src/amf/ngap-handler.c:1253)
07/30 22:53:38.408: [amf] INFO:     RAN_UE_NGAP_ID[0] AMF_UE_NGAP_ID[1] (../src/amf/ngap-handler.c:1255)
07/30 22:53:38.408: [amf] INFO:     SUCI[suci-0-724-03-0000-0-0-0000000005] (../src/amf/ngap-handler.c:1257)
07/30 22:53:38.408: [amf] INFO: [Removed] Number of gNB-UEs is now 0 (../src/amf/context.c:1835)
07/30 22:53:38.408: [amf] INFO: [Removed] Number of AMF-UEs is now 0 (../src/amf/context.c:1199)
07/30 23:02:07.884: [amf] INFO: gNB-N2[10.244.0.1] connection refused!!! (../src/amf/amf-sm.c:641)
07/30 23:02:07.884: [amf] INFO: [Removed] Number of gNBs is now 0 (../src/amf/context.c:894)
07/30 23:03:33.679: [amf] INFO: gNB-N2 accepted[10.244.0.1]:14925 in ng-path module (../src/amf/ngap-sctp.c:108)
07/30 23:03:33.679: [amf] INFO: gNB-N2 accepted[10.244.0.1] in master_sm module (../src/amf/amf-sm.c:593)
07/30 23:03:33.679: [amf] INFO: [Added] Number of gNBs is now 1 (../src/amf/context.c:866)
07/30 23:06:30.946: [amf] INFO: InitialUEMessage (../src/amf/ngap-handler.c:349)
07/30 23:06:30.946: [amf] INFO: [Added] Number of gNB-UEs is now 1 (../src/amf/context.c:1829)
07/30 23:06:30.946: [amf] INFO:     RAN_UE_NGAP_ID[0] AMF_UE_NGAP_ID[2] TAC[8101] CellID[0x35b68001] (../src/amf/ngap-handler.c:483)
07/30 23:06:30.946: [amf] INFO: [suci-0-724-03-0000-0-0-0000000005] Unknown UE by SUCI (../src/amf/context.c:1302)
07/30 23:06:30.946: [amf] INFO: [Added] Number of AMF-UEs is now 1 (../src/amf/context.c:1120)
07/30 23:06:30.946: [gmm] INFO: Registration request (../src/amf/gmm-sm.c:131)
07/30 23:06:30.946: [gmm] INFO: [suci-0-724-03-0000-0-0-0000000005]    SUCI (../src/amf/gmm-handler.c:72)
07/30 23:06:30.948: [gmm] WARNING: [suci-0-724-03-0000-0-0-0000000005] Cannot find SUCI [404] (../src/amf/gmm-sm.c:527)
07/30 23:06:30.948: [amf] WARNING: [suci-0-724-03-0000-0-0-0000000005] Registration reject [7] (../src/amf/nas-path.c:139)
07/30 23:06:30.951: [amf] INFO: UE Context Release [Action:3] (../src/amf/ngap-handler.c:1253)
07/30 23:06:30.951: [amf] INFO:     RAN_UE_NGAP_ID[0] AMF_UE_NGAP_ID[2] (../src/amf/ngap-handler.c:1255)
07/30 23:06:30.951: [amf] INFO:     SUCI[suci-0-724-03-0000-0-0-0000000005] (../src/amf/ngap-handler.c:1257)
07/30 23:06:30.951: [amf] INFO: [Removed] Number of gNB-UEs is now 0 (../src/amf/context.c:1835)
07/30 23:06:30.951: [amf] INFO: [Removed] Number of AMF-UEs is now 0 (../src/amf/context.c:1199)

AUSF logs:

root@master-node:/home/ims/Downloads/open5gs-0.2.1# kubectl logs open5gs-0-1627684304-ausf-0
Open5GS daemon v2.2.3

07/30 22:31:55.775: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/ausf.yaml' (../lib/app/ogs-init.c:129)
07/30 22:31:55.780: [app] INFO: AUSF initialize...done (../src/ausf/app.c:31)
07/30 22:31:55.780: [sbi] INFO: nghttp2_server() [10.244.0.216]:7777 (../lib/sbi/nghttp2-server.c:145)
07/30 22:31:56.782: [ausf] INFO: [f1fd3b0c-f185-41eb-99d2-4153d59bb01d] NF registred [Heartbeat:10s] (../src/ausf/nf-sm.c:199)
07/30 22:32:02.522: [ausf] INFO: [ef71f8dc-f185-41eb-9c43-450c5ccc3a55] (NRF-notify) NF registered (../src/ausf/nnrf-handler.c:177)
07/30 22:32:02.522: [ausf] INFO: [ef71f8dc-f185-41eb-9c43-450c5ccc3a55] (NRF-notify) NF Profile updated (../src/ausf/nnrf-handler.c:196)
07/30 22:53:38.405: [ausf] WARNING: [suci-0-724-03-0000-0-0-0000000005] Cannot find SUPI [404] (../src/ausf/ue-sm.c:126)
07/30 23:06:30.948: [ausf] WARNING: [suci-0-724-03-0000-0-0-0000000005] Cannot find SUPI [404] (../src/ausf/ue-sm.c:126)

UDM logs:

root@master-node:/home/ims/Downloads/open5gs-0.2.1# kubectl logs open5gs-0-1627684304-udm-0
Open5GS daemon v2.2.3

07/30 22:31:51.508: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/udm.yaml' (../lib/app/ogs-init.c:129)
07/30 22:31:51.511: [app] INFO: UDM initialize...done (../src/udm/app.c:31)
07/30 22:31:51.511: [sbi] INFO: nghttp2_server() [10.244.0.207]:7777 (../lib/sbi/nghttp2-server.c:145)
07/30 22:31:52.524: [sbi] WARNING: [7] Failed to connect to 10.102.237.200 port 7777: Connection refused (../lib/sbi/client.c:465)
07/30 22:32:02.520: [udm] WARNING: [ef71f8dc-f185-41eb-9c43-450c5ccc3a55] Retry to registration with NRF (../src/udm/nf-sm.c:161)
07/30 22:32:02.522: [udm] INFO: [ef71f8dc-f185-41eb-9c43-450c5ccc3a55] NF registred [Heartbeat:10s] (../src/udm/nf-sm.c:199)
07/30 22:32:13.726: [udm] INFO: [fcaf2074-f185-41eb-be6f-59816ff7e07f] (NRF-notify) NF registered (../src/udm/nnrf-handler.c:177)
07/30 22:32:13.726: [udm] INFO: [fcaf2074-f185-41eb-be6f-59816ff7e07f] (NRF-notify) NF Profile updated (../src/udm/nnrf-handler.c:196)
07/30 22:53:38.405: [udm] WARNING: [suci-0-724-03-0000-0-0-0000000005] HTTP response error [404] (../src/udm/nudr-handler.c:86)
07/30 23:06:30.948: [udm] WARNING: [suci-0-724-03-0000-0-0-0000000005] HTTP response error [404] (../src/udm/nudr-handler.c:86)

UDR logs:

root@master-node:/home/ims/Downloads/open5gs-0.2.1# kubectl logs open5gs-0-1627684304-udr-0
Open5GS daemon v2.2.3

07/30 22:32:13.720: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/udr.yaml' (../lib/app/ogs-init.c:129)
07/30 22:32:13.724: [dbi] INFO: MongoDB URI: 'mongodb://open5gs-0-1627684304-mongodb/open5gs' (../lib/dbi/ogs-mongoc.c:129)
07/30 22:32:13.724: [app] INFO: UDR initialize...done (../src/udr/app.c:31)
07/30 22:32:13.724: [sbi] INFO: nghttp2_server() [10.244.0.210]:7777 (../lib/sbi/nghttp2-server.c:145)
07/30 22:32:13.727: [udr] INFO: [fcaf2074-f185-41eb-be6f-59816ff7e07f] NF registred [Heartbeat:10s] (../src/udr/nf-sm.c:199)
07/30 22:53:38.405: [dbi] INFO: [imsi-724030000000005] Cannot find IMSI in DB (../lib/dbi/subscription.c:56)
07/30 22:53:38.405: [udr] WARNING: [imsi-724030000000005] Cannot find SUPI in DB (../src/udr/nudr-handler.c:67)
07/30 23:06:30.948: [dbi] INFO: [imsi-724030000000005] Cannot find IMSI in DB (../lib/dbi/subscription.c:56)
07/30 23:06:30.948: [udr] WARNING: [imsi-724030000000005] Cannot find SUPI in DB (../src/udr/nudr-handler.c:67)

open5gs pods multiple replicas (

hello,
question, not an issue really.
is it safe to scale pods to multiple replicas ? (default is 1 for all components) ?
I can see comment in values.yaml that RWM mode is required if scale is required. Does this apply really to all components pods ?
thanks,
j

Scalability in Open5Gs Chart

Hello there,

Is there a method for me to scale my open5gs functions, specifically UPF and SMF, so that I can handle more user equipment traffic?

Forwarding traffic between AMF/UPF and internet

Hello! Thanks for the great work on this project - much appreciated! I want to have internet on my subscriber phone. Therefore, I want to forward traffic from Open5gs to the internet and vise versa. Is there a way to configure Kubernetes that way?

NFs retrying to register to NRF (Open5GS 2.6.4)

Hello!
I was trying to see if I could run Open5GS version 2.6.4 but there seems to be a problem with the network functions not registering to the NRF. I installed the chart with the following command: helm install open5gs openverso/open5gs --version 2.0.12 --values=values.yaml

values.yaml:

hss:
  enabled: false
mme:
  enabled: false
pcrf:
  enabled: false
smf:
  config:
    pcrf:
      enabled: false
  image:
    tag: "2.6.4"
sgwc:
  enabled: false
sgwu:
  enabled: false
amf:
  config:
    guamiList:
      - plmn_id:
          mcc: "999"
          mnc: "70"
        amf_id:
          region: 2
          set: 1
    taiList:
      - plmn_id:
          mcc: "999"
          mnc: "70"
        tac:
          - 1
    plmnList:
      - plmn_id:
          mcc: "999"
          mnc: "70"
        s_nssai:
          - sst: 1
            sd: "0x111111"
  image:
    tag: "2.6.4"
ausf:
  image:
    tag: "2.6.4"
bsf:
  image:
    tag: "2.6.4"
nrf:
  image:
    tag: "2.6.4"
nssf:
  config:
    nsiList:
      - nrf:
          hostname: ""
          port: 7777
        sst: 1
        sd: "0x111111"
  image:
    tag: "2.6.4"
pcf:
  image:
    tag: "2.6.4"
udm:
  image:
    tag: "2.6.4"
udr:
  image:
    tag: "2.6.4"
upf:
  image:
    tag: "2.6.4"
webui:
  ingress:
    enabled: false
  image:
    tag: "2.6.4"
populate:
  image:
    tag: "0.10.3"
  enabled: true
  initCommands:
    - open5gs-dbctl add_ue_with_slice 999700000000001
      465B5CE8B199B49FAA5F0A2EE238A6BC E8ED289DEBA952E4283B54E88E6183CA internet
      1 111111
    - open5gs-dbctl add_ue_with_slice 999700000000002
      465B5CE8B199B49FAA5F0A2EE238A6BC E8ED289DEBA952E4283B54E88E6183CA internet
      1 111111

AMF logs:

NRF - only the NRF itself is registered:

When updating Open5GS web UI to 2.6.0 using populate the header says Open5GS 2.5.6

UERANSIM-UES 3.2.6 not working -> DNN Problem

Hello, so i have subscribed to imsi in the open5gs WebUI '999700000000001'. But in the ueransim-ue container appears this error. All other container logs seems fine

Connect the latest oai-gnb (w36) with open5gs

Hello! Thanks for such a great repository!
I followed your tutorial: Open5gs and OAI-GNB in https://gradiant.github.io/openverso-charts/open5gs-oaignb.html, and successfully connected my Redmi K30s with the open5gs core.
However, after several minutes, the phone lost its connection with the oai-gnb. I captured the traffic of amf pod and found that it received UEContextReleaseRequest from the gNB pod.
I thought there may be some bugs with the oai-gNB with tag 2022.w20, which was tested in this tutorial.
So I changed the tag field in the value.yaml of oai-gNB to 2022.w36, which was the latest one I found in your docker hub.
However, the deployment of this gNB pod failed, with the following logs:
root@5g-master:/home/osboxes# kubectl logs oai-gnb-0
GNB_NGA_IP_ADDRESS=10.244.37.124/32
GNB_NGU_IP_ADDRESS=10.244.37.124/32
check if open5gs-amf-ngap hostname is resolvable
open5gs-amf-ngap.default.svc.cluster.local has address 10.103.173.31
AMF_IP_ADDRESS=10.103.173.31
/opt/oai/bin/nr-softmodem.Rel15 -O /oai.conf --sa -E --continuous-tx

And the output of kubectl describe command was:
root@5g-master:/home/osboxes# kubectl describe pod oai-gnb-0
Name: oai-gnb-0
Namespace: default
Priority: 0
Node: 5g-node/192.168.5.3
Start Time: Fri, 28 Oct 2022 05:30:03 -0400
Labels: app.kubernetes.io/instance=oai-gnb
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=oai-gnb
controller-revision-hash=oai-gnb-65686dd886
helm.sh/chart=oai-gnb-0.3.1
statefulset.kubernetes.io/pod-name=oai-gnb-0
Annotations: cni.projectcalico.org/containerID: 736122d866353be53832d52edda0bf4d23bb8441849286063a57a391211ac07b
cni.projectcalico.org/podIP: 10.244.37.124/32
cni.projectcalico.org/podIPs: 10.244.37.124/32
Status: Running
IP: 10.244.37.124
IPs:
IP: 10.244.37.124
Controlled By: StatefulSet/oai-gnb
Containers:
oai-gnb:
Container ID: docker://26f27f7db08d3a0e13748b8eadffaea659c9e93d8b87c42719d21b5a370840bf
Image: docker.io/openverso/oai:2022.w36
Image ID: docker-pullable://openverso/oai@sha256:3e5cd69f80b2f1aa7882ee19a3ba4909c56b3832e8a0ebd65833c35e5fd8e5be
Port: 2152/UDP
Host Port: 0/UDP
Args:
/opt/oai/bin/nr-softmodem.Rel15
-O
/oai.conf
--sa
-E
--continuous-tx
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 132
Started: Fri, 28 Oct 2022 05:52:58 -0400
Finished: Fri, 28 Oct 2022 05:52:58 -0400
Ready: False
Restart Count: 9
Limits:
ettus.com/usrp: 1
Requests:
ettus.com/usrp: 1
Environment:
CONFIG_TEMPLATE_PATH: /opt/oai/etc/gnb.sa.tdd.conf
GNB_NGA_IF_NAME: eth0
GNB_NGU_IF_NAME: eth0
AMF_HOSTNAME: open5gs-amf-ngap
Mounts:
/opt/oai/etc from config (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-d52j7 (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: oai-gnb
Optional: false
kube-api-access-d52j7:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors:
Tolerations: ettus.com/usrp:NoSchedule
node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message

Normal Scheduled 27m default-scheduler Successfully assigned default/oai-gnb-0 to 5g-node
Normal Pulling 27m kubelet Pulling image "docker.io/openverso/oai:2022.w36"
Normal Pulled 25m kubelet Successfully pulled image "docker.io/openverso/oai:2022.w36" in 1m49.857430058s
Normal Created 24m (x5 over 25m) kubelet Created container oai-gnb
Normal Started 24m (x5 over 25m) kubelet Started container oai-gnb
Normal Pulled 24m (x4 over 25m) kubelet Container image "docker.io/openverso/oai:2022.w36" already present on machine
Warning BackOff 2m20s (x110 over 25m) kubelet Back-off restarting failed container

Could you please give me some help on deploying the latest version of oai-gnb pod? or give me some clues on why the gnb pod sends UEContextReleaseRequest to amf?
I also checked the logs of gNB, it said:
[NR_RRC] Removing UE 72af instance after UE_CONTEXT_RELEASE_Complete (ue_release_timer_rrc timeout)
[NR_MAC] [gNB 0] Remove NR UE_id 0: rnti 0x72af
[NR_MAC] to remove in mac rnti_to_remove[0] = 0x72af
[GTPU] [0] Deleted all tunnels for RNTI 72af (1 tunnels deleted)
[RRC] [FRAME 00857][eNB][MOD 00][RNTI 72af] Removed UE context
[NR_RRC] remove UE 72af
[NR_PHY] to remove rnti 0x72af
[NR_PHY] to remove rnti_to_remove_count=1, up_removed=1 down_removed=0 pucch_removed=0

Then my UE was lost.
I appreciate it so much if you can help me! Thanks in advance!

SCTP does not establish connections between pods on different nodes.

I have an experiment running with Open5GS that works perfectly with Flannel; however, when I switch to Cilium, I can no longer establish a connection between the eight Ueransim pods and the AMF using SCTP. I noticed that UERANSIM and AMF work when they are on the same node, but they do not function when on different nodes.

flowchart TB
    subgraph node1
        direction LR
        ueransim02
        ueransim03
        ueransim04
    end
     subgraph node2
        direction LR
        ueransim05
        ueransim06
        ueransim07
        ueransim08
    end
    subgraph node3
        direction LR
        ueransim01 
        amf
    end
    ueransim01 == OK ==> amf
    ueransim02 -.-> amf
    ueransim03 -.-> amf
    ueransim04 -.-> amf
    ueransim05 -.-> amf
    ueransim06 -.-> amf
    ueransim07 -.-> amf
    ueransim08 -.-> amf
    linkStyle 1,2,3,4,5,6,7 stroke:red,color:red;
    linkStyle 0 stroke:green;

Issue in installing Open5GS on a Kubernetes cluster by openverso helm chart

Hi,

I am trying to install Open5GS core on a kubernetes cluster by using helm charts. I am following "https://gradiant.github.io/openverso-charts/open5gs-srslte.html" to setup open5gs with srslte. I tried to install by executing:

"helm upgrade --install open5gs openverso/open5gs --version 1.2.1 --values https://gradiant.github.io/openverso-charts/docs/open5gs-srslte/epc-values.yaml"

But after executing this all the pods are not running. open5gs-mongodb pod is in Pending state. The following pods are in CrashLoopBackOff state: open5gs-hss, open5gs-pcrf. And open5gs-webui pod is in Init:CrashLoopBackOff state.

Here is the logs of open5gs-hss pod:

"08/09 14:18:14.303: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/hss.yaml' (../lib/app/ogs-init.c:126)
08/09 14:18:15.346: [dbi] WARNING: Failed to connect to server [mongodb://open5gs-mongodb/open5gs] (../lib/dbi/ogs-mongoc.c:122)
08/09 14:18:15.346: [app] WARNING: Failed to intialize HSS (../src/hss/app-init.c:28)
"

Here is the log of open5gs-pcrf pod:
"
08/09 14:19:56.304: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/pcrf.yaml' (../lib/app/ogs-init.c:126)
08/09 14:19:57.362: [dbi] WARNING: Failed to connect to server [mongodb://open5gs-mongodb/open5gs] (../lib/dbi/ogs-mongoc.c:122)
08/09 14:19:57.362: [app] WARNING: Failed to intialize PCRF (../src/pcrf/app-init.c:28)
"

Here is the log of init container in open5gs-webui pod:
"
add admin user with password 1423 if no users
MongoDB shell version v4.4.1
connecting to: mongodb://open5gs-mongodb:27017/open5gs?compressors=disabled&gssapiServiceName=mongodb
Error: couldn't connect to server open5gs-mongodb:27017, connection attempt failed: SocketException: Error connecting to open5gs-mongodb:27017 (10.97.165.10:27017) :: caused by :: Connection refused :
connect@src/mongo/shell/mongo.js:374:17
@(connect):2:6
exception: connect failed
exiting with code 1
"

Here is the log of webui container in open5gs-webui pod:
"Error from server (BadRequest): previous terminated container "webui" in pod "open5gs-webui-5747c779d-xlkqs" not found
"

Output of "$ kubectl exec -it open5gs-mongodb-75f88f5464-wb6ff bash " is:
"
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
Error from server (BadRequest): pod open5gs-mongodb-75f88f5464-wb6ff does not have a host assigned
"

Output of "$ kubectl describe pod open5gs-mongodb-75f88f5464-wb6ff" shows FailedScheduling warning with this message:

0/3 nodes are available: 3 pod has unbound immediate PersistentVolumeClaims. preemption: 0/3 nodes are available: 3 Preemption is not helpful for scheduling.

Looks like the issue is related to mongodb. Please let me know how to solve this.

Thanks.

CrashLoopBackOff for 5gscore pods

Hello, I am trying to run these helm charts on AKS but I have an issue in which not all pods become available, and fail with status error "CrashLoopBackOff", as shown in the image below;

The actual error message for the containers running inside the pods is as follows:

Open5GS daemon v2.3.3

11/18 15:02:12.841: [app] INFO: Configuration: '/opt/open5gs/etc/open5gs/amf.yaml' (../lib/app/ogs-init.c:129)
11/18 15:02:12.855: [sbi] INFO: nghttp2_server() [10.1.0.18]:7777 (../lib/sbi/nghttp2-server.c:144)
11/18 15:02:12.865: [sock] ERROR: socket create(2:1:132) failed (93:Protocol not supported) (../lib/core/ogs-socket.c:87)
11/18 15:02:12.865: [sock] FATAL: ogs_sctp_socket: Assertion `new' failed. (../lib/sctp/ogs-lksctp.c:45)
11/18 15:02:12.865: [core] FATAL: backtrace() returned 10 addresses (../lib/core/ogs-abort.c:37)
/usr/local/lib/x86_64-linux-gnu/libogssctp.so.2(ogs_sctp_socket+0x98) [0x7f14f7a43e06]
/usr/local/lib/x86_64-linux-gnu/libogssctp.so.2(ogs_sctp_server+0x11e) [0x7f14f7a441c8]
open5gs-amfd(+0x18eaf) [0x55e9d0a73eaf]
open5gs-amfd(+0x1a0de) [0x55e9d0a750de]
open5gs-amfd(+0x699b) [0x55e9d0a6199b]
open5gs-amfd(+0x5f3b) [0x55e9d0a60f3b]
open5gs-amfd(+0x6718) [0x55e9d0a61718]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f14f70c1d0a]
open5gs-amfd(+0x5e5a) [0x55e9d0a60e5a]

Apparently, the pods are not able to start due to "Protocol not supported" error.

Any clues on what might be causing this behaviour?

Add framed routing to ueransim and open5gs

I will leave here an article on what I am talking about.

https://github.com/s5uishida/open5gs_5gc_ueransim_framed_routing_sample_config

multiple UPFs on 5GC in smf.yaml

Hi,
i wanted to setup 5G core with having 2 UPFs, each serving single DNN. I.e. one upf is to be instantiated on cluster with rest of 5gc, and other would be instantiated as standalone on different cluster (i.e. Edge).
I am stuck on how to set smf configuration to be aware of both UPF PFCP IPs . I would need to define list of pfcp ip and relate it to DNN. I'd need something in smf.yaml like:

 upf:
     pfcp:
       - addr: upf1-ip
           dnn: internet
       - addr: upf2-ip
           dnn: compX-apn

For what i can see, in smf.yaml config file there is only option to define single upf pfcp ip (and not list).
I might be able to do some crude code rewrite in resources/smf.yaml to support multiple UPFs (And related DNNs), but i was wondering if this is already supported in different way.
I can see variable .Values.customOpen5gsConfig but not sure how to put config file in there. Seems that way would not trigger resolving of helm variables.
Any suggestion ?
br,
j

[sctp] [error]: could not connect: Connection timed out

Hi,

I am getting the SCTP could not connect: Connection timed out Error after deploying the open5gs and ueransim charts.

Chain of events :

I deployed the open5gs chart
I created a subscriber in the GUI
I deployed the ueransim chart

All components are deployed in the same namespace called open5gs namespace.
Below are all needed info.

Open5gs
This is thevalues.yaml file :

I changed the sd: "ffffff" to be sd: "1" to match the UERANSIM value

image:
  registry: docker.io
  repository: openverso/open5gs
  tag: 2.3.3
  pullPolicy: IfNotPresent
webui:
  image:
    registry: docker.io
    repository: openverso/open5gs-webui
    tag: 2.3.3
    pullPolicy: IfNotPresent
  enabled: true
  resources: {}
  ingress:
    enabled: true  
    certManager: false
    pathType: ImplementationSpecific
    hostname:
    path: /
    annotations: {}
    tls: false
hss:
  enabled: false
  resources: {}
  ### For reference, see `open5gs.yaml`
  logger:
    level: info
    # domain: core,diameter
mme:
  enabled: false
  resources: {}
  logger:
    level: info
  parameter: {}
  gummei:
    plmn_id:
      mcc: 100
      mnc: 10
    mme_gid: 2
    mme_code: 1
  tai:
    plmn_id:
      mcc: 100
      mnc: 10
    tac: 1

  externalService:
    enabled: false
    type: LoadBalancer
    loadBalancerSourceRanges: []
    loadBalancerIP:
    externalTrafficPolicy: Local

sgwc:
  enabled: false
  resources: {}
  logger:
    level: info
    # domain: core,diameter
  parameter:
    no_ipv6: true
  max: {}
  pool: {}

sgwu:
  enabled: false
  resources: {}
  logger:
    level: info
    # domain: core,diameter
  parameter:
    no_ipv6: true
  max: {}
  pool: {}
  externalService:
    enabled: false
    advertiseDomain: "ext.openverso.org"
    type: LoadBalancer
    loadBalancerSourceRanges: []
    loadBalancerIP:
    externalTrafficPolicy: Local

amf:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}
  guami:
  - plmn_id:
      mcc: 901
      mnc: 70
    amf_id:
      region: 2
      set: 1
  tai:
  - plmn_id:
      mcc: 901
      mnc: 70
    tac: 1
  plmn_support:
  - plmn_id:
      mcc: 901
      mnc: 70
    s_nssai:
      - sst: "1"
        sd: "1"
  externalService:
    enabled: false
    advertiseDomain: "ext.openverso.org"
    type: LoadBalancer
    loadBalancerSourceRanges: []
    loadBalancerIP:
    externalTrafficPolicy: Local

smf:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}
  pdn:
    addr: 10.45.0.1/16

upf:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}
  pdn:
    addr: 10.45.0.1/16
  externalService:
    enabled: false
    advertiseDomain: "ext.openverso.org"
    type: LoadBalancer
    loadBalancerSourceRanges: []
    loadBalancerIP:
    externalTrafficPolicy: Local

nrf:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}

udr:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}

udm:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}

ausf:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}

nssf:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}
  nsi:
  - sst: "1"
    sd: "1"

bsf:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}

pcf:
  enabled: true
  resources: {}
  logger:
    level: info
  parameter: {}

pcrf:
  enabled: true
  resources: {}
  logger:
    level: info
    # domain: core,diameter
  parameter:

mongodb:
  # mongodb.enabled -- set to 'false' to disable automatically deploying dependent charts
  enabled: true
  auth:
    enabled: false

securityPolicy:
  enabled: false

UERANSIM

This is the values.yaml file :
I changed these values:

tac: '0001' -> tac: '1' matching it with amf configuration from open5gs
amf: open5gs-amf -> amf: core5g-open5gs-amf because core5g is the my Helm release name and it is added to the K8s service name.

global:
  imageRegistry:
 
  imagePullSecrets: []
  storageClass:

kubeVersion:
nameOverride:
fullnameOverride:
commonLabels: {}
commonAnnotations: {}
clusterDomain: cluster.local
extraDeploy: []

image:
  registry: docker.io
  repository: openverso/ueransim
  tag: 3.2.2

  pullPolicy: IfNotPresent

  pullSecrets: []

  debug: false


mcc: '901'
mnc: '70'
tac: '1'

UECount: 4
initialMSISDN: '0000000001'
key: 465B5CE8B199B49FAA5F0A2EE238A6BC
op: E8ED289DEBA952E4283B54E88E6183CA
opType: OPC
apn: internet
sst: 1
sd: ffffff

amf: core5g-open5gs-amf


resources:
  limits: {}
  requests: {}

podSecurityContext:
  enabled: false

containerSecurityContext:
  enabled: false

podLabels: {}
podAnnotations: {}
affinity: {}
nodeSelector: {}
tolerations: []
updateStrategy:
  type: RollingUpdate

Subscriber configuration in GUI

My Environemnt:

2 Vagrant Boxes (Debian GNU/Linux 10 (buster))
K8s v1.20.11
docker v20.10.10
Helm v3

NAME    STATUS   ROLES                  AGE    VERSION    INTERNAL-IP     EXTERNAL-IP   OS-IMAGE                       KERNEL-VERSION    CONTAINER-RUNTIME
kube1   Ready    control-plane,master   140m   v1.20.12   172.16.16.100   <none>        Debian GNU/Linux 10 (buster)   4.19.0-16-amd64   docker://20.10.10
kube2   Ready    <none>                 140m   v1.20.12   172.16.16.101   <none>        Debian GNU/Linux 10 (buster)   4.19.0-16-amd64   docker://20.10.10

Logs from gnodeb container

k exec -it ueransim-0 -c gnodeb -n open5gs -- /bin/bash

NOTE: 10.105.160.161 is the IP of the AMF K8s service

Launching gnb: nr-gnb -c gnb.yaml
UERANSIM v3.2.2
[2021-10-28 13:17:55.872] [sctp] [info] Trying to establish SCTP connection... (10.105.160.161:38412)
[2021-10-28 13:17:56.846] [rrc] [debug] UE[1] new signal detected
[2021-10-28 13:17:56.846] [rrc] [debug] UE[2] new signal detected
[2021-10-28 13:17:56.848] [rrc] [debug] UE[3] new signal detected
[2021-10-28 13:17:56.852] [rrc] [debug] UE[4] new signal detected
[2021-10-28 13:23:00.171] [sctp] [error] Connecting to 10.105.160.161:38412 failed. SCTP could not connect: Connection timed out

Logs from ues container

k exec -it ueransim-0 -c ues -n open5gs -- /bin/bash

Launching ue: nr-ue -c ue.yaml
UERANSIM v3.2.2
[2021-10-28 13:17:55.842] [901700000000003|nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2021-10-28 13:17:55.844] [901700000000001|nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2021-10-28 13:17:55.845] [901700000000004|nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2021-10-28 13:17:55.847] [901700000000002|nas] [info] UE switches to state [MM-DEREGISTERED/PLMN-SEARCH]
[2021-10-28 13:17:56.846] [901700000000003|rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2021-10-28 13:17:56.847] [901700000000003|nas] [info] Selected plmn[901/70]
[2021-10-28 13:17:56.847] [901700000000003|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:17:56.847] [901700000000003|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:17:56.847] [901700000000003|rrc] [error] Cell selection failure, no suitable or acceptable cell found
[2021-10-28 13:17:56.847] [901700000000004|rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2021-10-28 13:17:56.847] [901700000000004|nas] [info] Selected plmn[901/70]
[2021-10-28 13:17:56.847] [901700000000004|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:17:56.847] [901700000000004|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:17:56.847] [901700000000004|rrc] [error] Cell selection failure, no suitable or acceptable cell found
[2021-10-28 13:17:56.848] [901700000000001|rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2021-10-28 13:17:56.848] [901700000000001|nas] [info] Selected plmn[901/70]
[2021-10-28 13:17:56.848] [901700000000001|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:17:56.848] [901700000000001|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:17:56.848] [901700000000001|rrc] [error] Cell selection failure, no suitable or acceptable cell found
[2021-10-28 13:17:56.852] [901700000000002|rrc] [debug] New signal detected for cell[1], total [1] cells in coverage
[2021-10-28 13:17:56.853] [901700000000002|nas] [info] Selected plmn[901/70]
[2021-10-28 13:17:56.853] [901700000000002|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:17:56.853] [901700000000002|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:17:56.853] [901700000000002|rrc] [error] Cell selection failure, no suitable or acceptable cell found
[2021-10-28 13:18:01.348] [901700000000001|nas] [info] UE switches to state [MM-DEREGISTERED/NO-CELL-AVAILABLE]
[2021-10-28 13:18:01.348] [901700000000004|nas] [info] UE switches to state [MM-DEREGISTERED/NO-CELL-AVAILABLE]
[2021-10-28 13:18:01.348] [901700000000003|nas] [info] UE switches to state [MM-DEREGISTERED/NO-CELL-AVAILABLE]
[2021-10-28 13:18:01.350] [901700000000002|nas] [info] UE switches to state [MM-DEREGISTERED/NO-CELL-AVAILABLE]
[2021-10-28 13:18:28.362] [901700000000002|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:18:28.362] [901700000000002|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:18:28.362] [901700000000002|rrc] [error] Cell selection failure, no suitable or acceptable cell found
[2021-10-28 13:18:28.362] [901700000000003|rrc] [warning] Suitable cell selection failed in [1] cells. [0] out of PLMN, [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:18:28.362] [901700000000003|rrc] [warning] Acceptable cell selection failed in [1] cells. [0] no SI, [0] reserved, [1] barred, ftai [0]
[2021-10-28 13:18:28.362] [901700000000003|rrc] [error] Cell selection failure, no suitable or acceptable cell found

MongoDB failing

Hi everyone,
I've used the chart to start open5gs.
I have created a PV of 8GB with ReadWriteOnce. However, MongoDB is reported in CrashLoopBackoff state.
Below the logs are reported:

"t":{"$date":"2023-03-21T09:44:47.307+00:00"},"s":"I", "c":"CONTROL", "id":20698, "ctx":"-","msg":"***** SERVER RESTARTED ***"}
{"t":{"$date":"2023-03-21T09:44:47.307+00:00"},"s":"I", "c":"NETWORK", "id":4915701, "ctx":"-","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":true}}}
{"t":{"$date":"2023-03-21T09:44:47.309+00:00"},"s":"I", "c":"CONTROL", "id":23285, "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
{"t":{"$date":"2023-03-21T09:44:47.309+00:00"},"s":"W", "c":"ASIO", "id":22601, "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"}
{"t":{"$date":"2023-03-21T09:44:47.309+00:00"},"s":"I", "c":"NETWORK", "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize."}
{"t":{"$date":"2023-03-21T09:44:47.310+00:00"},"s":"W", "c":"ASIO", "id":22601, "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"}
{"t":{"$date":"2023-03-21T09:44:47.310+00:00"},"s":"I", "c":"REPL", "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationDonorService","ns":"config.tenantMigrationDonors"}}
{"t":{"$date":"2023-03-21T09:44:47.310+00:00"},"s":"I", "c":"REPL", "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationRecipientService","ns":"config.tenantMigrationRecipients"}}
{"t":{"$date":"2023-03-21T09:44:47.310+00:00"},"s":"I", "c":"CONTROL", "id":5945603, "ctx":"main","msg":"Multi threading initialized"}
{"t":{"$date":"2023-03-21T09:44:47.311+00:00"},"s":"I", "c":"CONTROL", "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1,"port":27017,"dbPath":"/bitnami/mongodb/data/db","architecture":"64-bit","host":"open5gs-1679391857-mongodb-574f6d8447-6dzsr"}}
{"t":{"$date":"2023-03-21T09:44:47.311+00:00"},"s":"I", "c":"CONTROL", "id":23403, "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"5.0.10","gitVersion":"bbf5bc7e16d1713c9349a09adf4901ca37472e66","openSSLVersion":"OpenSSL 1.1.1n 15 Mar 2022","modules":[],"allocator":"tcmalloc","environment":{"distmod":"debian11","distarch":"x86_64","target_arch":"x86_64"}}}}
{"t":{"$date":"2023-03-21T09:44:47.311+00:00"},"s":"I", "c":"CONTROL", "id":51765, "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"","version":"Kernel 5.13.19-2-MANJARO"}}}
{"t":{"$date":"2023-03-21T09:44:47.311+00:00"},"s":"I", "c":"CONTROL", "id":21951, "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"config":"/opt/bitnami/mongodb/conf/mongodb.conf","net":{"bindIp":"","ipv6":false,"port":27017,"unixDomainSocket":{"enabled":true,"pathPrefix":"/opt/bitnami/mongodb/tmp"}},"processManagement":{"fork":false,"pidFilePath":"/opt/bitnami/mongodb/tmp/mongodb.pid"},"security":{"authorization":"disabled"},"setParameter":{"enableLocalhostAuthBypass":"true"},"storage":{"dbPath":"/bitnami/mongodb/data/db","directoryPerDB":false,"journal":{"enabled":true}},"systemLog":{"destination":"file","logAppend":true,"logRotate":"reopen","path":"/opt/bitnami/mongodb/logs/mongodb.log","quiet":false,"verbosity":0}}}}
{"t":{"$date":"2023-03-21T09:44:47.312+00:00"},"s":"I", "c":"STORAGE", "id":22315, "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=7455M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),builtin_extension_config=(zstd=(compression_level=6)),file_manager=(close_idle_time=600,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress,compact_progress],"}}
{"t":{"$date":"2023-03-21T09:44:47.883+00:00"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":17,"message":"[1679391887:883900][1:0x7f1070e88c80], connection: __posix_open_file, 808: /bitnami/mongodb/data/db/WiredTiger.wt: handle-open: open: File exists"}}
{"t":{"$date":"2023-03-21T09:44:47.885+00:00"},"s":"I", "c":"STORAGE", "id":22430, "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"unexpected file WiredTiger.wt found, renamed to WiredTiger.wt.18"}}
{"t":{"$date":"2023-03-21T09:44:47.886+00:00"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":1,"message":"[1679391887:886264][1:0x7f1070e88c80], connection: __posix_open_file, 808: /bitnami/mongodb/data/db/WiredTiger.wt: handle-open: open: Operation not permitted"}}
{"t":{"$date":"2023-03-21T09:44:47.948+00:00"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":17,"message":"[1679391887:948844][1:0x7f1070e88c80], connection: __posix_open_file, 808: /bitnami/mongodb/data/db/WiredTiger.wt: handle-open: open: File exists"}}
{"t":{"$date":"2023-03-21T09:44:47.952+00:00"},"s":"I", "c":"STORAGE", "id":22430, "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"unexpected file WiredTiger.wt found, renamed to WiredTiger.wt.19"}}
{"t":{"$date":"2023-03-21T09:44:47.953+00:00"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":1,"message":"[1679391887:953160][1:0x7f1070e88c80], connection: __posix_open_file, 808: /bitnami/mongodb/data/db/WiredTiger.wt: handle-open: open: Operation not permitted"}}
{"t":{"$date":"2023-03-21T09:44:48.040+00:00"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":17,"message":"[1679391888:40235][1:0x7f1070e88c80], connection: __posix_open_file, 808: /bitnami/mongodb/data/db/WiredTiger.wt: handle-open: open: File exists"}}
{"t":{"$date":"2023-03-21T09:44:48.044+00:00"},"s":"I", "c":"STORAGE", "id":22430, "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"unexpected file WiredTiger.wt found, renamed to WiredTiger.wt.20"}}
{"t":{"$date":"2023-03-21T09:44:48.045+00:00"},"s":"E", "c":"STORAGE", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error","attr":{"error":1,"message":"[1679391888:44997][1:0x7f1070e88c80], connection: __posix_open_file, 808: /bitnami/mongodb/data/db/WiredTiger.wt: handle-open: open: Operation not permitted"}}
{"t":{"$date":"2023-03-21T09:44:48.047+00:00"},"s":"W", "c":"STORAGE", "id":22347, "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."}
{"t":{"$date":"2023-03-21T09:44:48.048+00:00"},"s":"F", "c":"STORAGE", "id":28595, "ctx":"initandlisten","msg":"Terminating.","attr":{"reason":"1: Operation not permitted"}}
{"t":{"$date":"2023-03-21T09:44:48.048+00:00"},"s":"F", "c":"-", "id":23091, "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":28595,"file":"src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp","line":687}}
{"t":{"$date":"2023-03-21T09:44:48.048+00:00"},"s":"F", "c":"-", "id":23092, "ctx":"initandlisten","msg":"\n\naborting after fassert() failure\n\n"}

I am opening the issue here because I suspect is something related to the configuration of PVs. The PVC is correctly bound, but I am not able to bring up MongoDB without failure, and this causes a cascading failure on the other components. Any clue?
I am running on a Kubernetes 1.23.4 cluster, Manjaro system for the control plane. The cluster is made of a single node.

Set static ips for each network function via values.yaml

Hello,

we are using your Charts to do a bit of research regarding security in containerized 5G networks, using tools like Falco.

For convince sake, even tho its not the best practice, we would like to give each Network function an predefined static IP address in our Kubernetes Cluster. Is this achievable via the values.yaml of the open5gs helm chart ?

UPF running on separate cluster - exposing requird service for communication SMF-UPF

Hi,
currently I have UPF running on same cluster as other components. UPF is having separate data/N3 interface (same as uernasim/gNB) and communication is working fine.
I would need to separate UPF to differenet cluster since upf would be located on edge. For this i would need to expose some services as external ones via LB and explicitly define them in config files (since service autodiscovery no longer works).
For what i figured out, only services required to be external is upf-pfcp and smf-pcfp, for communication between SMF and UPF.
(port TCP 8805 on both sides).
I set static ips on LB side, so i could use those determinisitic IPs for upf-pfcf and smf-pfcp, i used in upf and smf config parts instead of K8s service name.
I tried this but didn't work. I could only find partial logs from smf that i took ( pasted below).
I will have to redo setup, but putting question up front just perhaps to get confirmation if pcfp service on both sides is the only service requred for scenario with upf separated ? and using those in config sections of upf and smf.
if i remember corrctly, system crate gtpu service as well, but that is useless since it points to ip hosted on multus interface is used.
thanks for any guideline on this.

br,
j

09/25 10:11:49.436: [smf] INFO: PFCP associated (../src/smf/pfcp-sm.c:174)
09/25 10:11:49.450: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:11:49.489: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:11:50.748: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:11:50.748: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:11:53.236: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:11:53.236: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:11:53.441: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:11:53.481: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:11:54.040: [pfcp] INFO: ogs_pfcp_connect() [100.96.1.1]:51209 (../lib/pfcp/path.c:61)
09/25 10:11:54.040: [smf] WARNING: cannot handle PFCP message type[1] (../src/smf/pfcp-sm.c:140)
09/25 10:11:54.748: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:11:54.748: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:11:56.542: [pfcp] WARNING: [2] REMOTE Request Duplicated. Discard! for step 1 type 1 peer [100.96.1.1]:51209 (../lib/pfcp/xact.c:402)
09/25 10:11:57.236: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:11:57.236: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:11:57.434: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:11:57.473: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:11:58.748: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:11:58.748: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:11:59.041: [pfcp] WARNING: [2] REMOTE Request Duplicated. Discard! for step 1 type 1 peer [100.96.1.1]:51209 (../lib/pfcp/xact.c:402)
09/25 10:12:01.236: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:12:01.236: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:12:01.426: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:12:01.473: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:12:01.540: [pfcp] WARNING: [4] LOCAL No Reponse. Give up! for step 1 type 1 peer [100.96.1.1]:13214 (../lib/pfcp/xact.c:613)
09/25 10:12:01.540: [smf] WARNING: No Heartbeat from UPF [100.96.1.1]:13214 (../src/smf/pfcp-sm.c:304)
09/25 10:12:01.540: [smf] INFO: PFCP de-associated (../src/smf/pfcp-sm.c:179)
09/25 10:12:01.543: [smf] INFO: PFCP associated (../src/smf/pfcp-sm.c:174)
09/25 10:12:02.748: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:12:02.748: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:12:05.236: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:12:05.236: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:12:05.419: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:12:05.465: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:12:06.748: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:12:06.748: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:12:07.095: [smf] INFO: [82947024-3cba-41ed-ae42-1bbbd58b3a96] (NRF-notify) NF registered (../src/smf/nnrf-handler.c:181)
09/25 10:12:07.095: [smf] INFO: [82947024-3cba-41ed-ae42-1bbbd58b3a96] (NRF-notify) NF Profile updated (../src/smf/nnrf-handler.c:202)
09/25 10:12:07.941: [pfcp] WARNING: [5] LOCAL No Reponse. Give up! for step 1 type 1 peer [192.168.25.25]:8805 (../lib/pfcp/xact.c:613)
09/25 10:12:07.941: [smf] WARNING: No Heartbeat from UPF [192.168.25.25]:8805 (../src/smf/pfcp-sm.c:304)
09/25 10:12:07.941: [smf] INFO: PFCP de-associated (../src/smf/pfcp-sm.c:179)
09/25 10:12:07.942: [smf] INFO: PFCP associated (../src/smf/pfcp-sm.c:174)
09/25 10:12:09.236: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)
09/25 10:12:09.236: [smf] ERROR: ogs_gtp2_parse_msg() failed (../src/smf/smf-sm.c:103)
09/25 10:12:09.410: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:12:09.458: [smf] ERROR: Not supported version[2] (../src/smf/pfcp-path.c:128)
09/25 10:12:10.748: [gtp] WARNING: Not implmeneted(type:110) (../lib/gtp/v2/message.c:2849)

TLS on SBI Interfaces

Hi!

I am trying to configure and enable TLS in SBI interfaces. I used your project to deploy Open5GS inside a kubernetes cluster. I started by changing the config files, setting the "no_tls" value to "false".

After that i used openssl to generate the CA and create certificates to the NFs (i only created for the AUSF for now). Then i tried to move the ca.crt, ausf.key and ausf.crt to the pod container of the AUSF with the command:

kubectl cp file-spec-src file-spec-dest -c specific-container

However, i was getting erros due to permissions, and even when i tried to move to the /tmp directory, everytime i restarted the pod, the files just got deleted so it was not a solution. So i tried this, with "no_tls" as "true", so it can create the pod AND to create the certificates in the /tmp/tls directory:

and then run this command

helm upgrade --install -f open5gs.yaml open5gs openverso/open5gs -n open5gs ,

And then run it again, but with value of "false"

and then run this command again

helm upgrade --install -f open5gs.yaml open5gs openverso/open5gs -n open5gs

Now when i go into the /tmp/tls directory i see the certificates. (I checked with cat and the certificates seem all okay):

and when i look into the ausf.yaml file it looks like this

However, isn't the ausf.yaml file supposed to have the path of certificates?

Also, how can i check if tls is actually working with curl? When i executed curl commands with https i get an error:

Can someone help me on this please?

Regards,
Luís Loureiro

Add a sidecar container to NFs

I have created a sidecar container image. I want to run this image as a sidecar container in NF such as amf. How can I modify AMF's chart to add my sidecar container?

gradiant / 5g-charts Goto Github PK

5g-charts's People

Contributors

Stargazers

Watchers

Forkers

5g-charts's Issues

Recommend Projects

Recommend Topics

Recommend Org