-
Notifications
You must be signed in to change notification settings - Fork 606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] About the order to start SMF and UPF #170
Comments
In 3GPP's specification, both UPF and SMF can send PFCP Association Setup Request. But in free5GC's recently design, only SMF will send PFCP Association Setup Request according to the UPF's IP inside the config file. As the result, UPF should start before SMF. |
Hi @calee0219 Thank you very much for your information. OK. I will start and use it in the order of SMF after UPF. For your reference, I'm using the following for the VM for UPF here.
|
Hi @free5gc-org , @calee0219 Please close this issue when this information "the order of SMF after UPF" was written on the Wiki. Thank you very much in advance. |
We updated it in: |
I am using two UPF in different VM and two SMF in the same VM. Though I started two upf first but getting the same error !!! |
@free5gc-org can you please give me the solution? |
Maybe is better to create another issue and reference to this issue so that it will not be ignore easily. |
Hi @free5gc-org
I have one question.
After starting C-Plane (except for UPF) on one VM first, then starting U-Plane (UPF only) on another VM, and then trying to register UE after NG-Setup of gNB, the following error occurred between SMF and UPF. As a result, creating a PDU session failed.
On the other hand, if starting UPF first and then C-Plane, the PDU session was created successfully.
Is this the specification? Or am I misunderstanding?
If it is the specification, I think it will be very easy to use if the specification is changed so that it does not depend on the order of starting SMF and UPF.
Thank you very much in advance.
The text was updated successfully, but these errors were encountered: