-
Notifications
You must be signed in to change notification settings - Fork 201
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
N2: Connection to AMF on 127.0.1.100:38412 completed can't continue #973
Comments
I'm not sure whether this is normal |
you need to set the TAI correctly. |
Thanks. I download the amf.yaml accorrding to the link, but when loading, it doesn't run. |
just update your own config according to the tutorial. it shows the parameters that need to be set correctly. |
Thanks. Maybe I have the same problem as the issue 'UE not registered to srsran gnb #896', which still don't have a conclusion. |
Issue Description
[Describe the issue in detail]
Follow the official example, I got the result as below:
N2: Connection to AMF on 127.0.1.100:38412 completed. The ubuntu stopped, without any further prompts.
I'm sure that firewall is down.
Setup Details
[Specify details of the test setup. This would help us reproduce the problem reliably]
e.g. Network configuration, Operation System, Hardware, RF front-end, library and driver versions
Expected Behavior
[What you expect to happen]
Cell pci=1, bw=20 MHz, 1T1R, dl_arfcn=627340 (n78), dl_freq=3410.1 MHz, dl_ssb_arfcn=626976, ul_freq=3410.1 MHz
N2: Connection to AMF on 127.0.1.100:38412 completed
==== gNB started ===
Type to view help
I can't see the "==== gNB started ===" on the panel
Actual Behaviour
[What happens instead e.g. error message]
Steps to reproduce the problem
[Tell us how to reproduce this issue e.g. RF setup, application config files]
Additional Information
[Any additional information, configuration or data that might be necessary to reproduce the issue]
The text was updated successfully, but these errors were encountered: