search

Orange-OpenSource / towards5gs-helm

Helm charts for deploying 5G network services on Kubernetes
Other
166 stars 130 forks source link

AMF、SMF and UPF failed to connect to internet #74

Closed linin00 closed 1 year ago

linin00 commented 1 year ago

I deployed 5GC by referring to this article, but all the network elements except amf and smf started successfully. Checking found that both amf and smf are stuck in the initialization process because the process of initializing the container wait-nrf keeps curl http://nrf-nnrf:8000, but the status code returned is 000. I tried to ping google.com in amf, smf and upf pod by exec command, but it will show ping: bad address 'google.com'. It looks like all pods with multiple NICs deployed, their network functionality is broken, how can I solve this problem? Thanks!

image

pinoOgni commented 1 year ago

Hi @linin00 it happened to me too and I think it depends on the MACVLAN cni-plugin you have installed. In my case a wrong version was downloaded or maybe corrupted I don't know. Indeed I tried copying the macvlan binary from another cluster where free5gc was running and after deleting and reinstalling free5gc again the pods started working.

sergirem commented 1 year ago

Hi @pinoOgni , I had the same issue but I do not understand how did you fix this error

Could you please explain me how to solve that problem?

Kind regards

pinoOgni commented 1 year ago

Hi @sergirem, I hope I remember correctly.

Basically I already had a working cluster on GCP and after creating the second one, that error appeared. After investigating, I had found that all the versions of the various components between the two clusters were identical.

I found that the error was about the macvlan, so the idea was to copy the cni plugin macvlan from the working cluster (I seem to remember that I only took that but perhaps I had also copied the multus one) and bring it to the cluster where I had the problem . Basically I copied the macvlan binary of the /opt/cni/bin directory.

I don't think it's the most correct solution but at that moment it was the only idea in mind and it went well.

github-actions[bot] commented 1 year ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 1 year ago

This issue was closed because it has been inactive for 14 days since being marked as stale.