Codent0101
commented
1 year ago To further troubleshoot this issue I have re-installed the software and used the quickstart guide and it appears to be an issue with the formatting of the NSSF.yml configuration file. All other services are alarm free. The only change I have made is the file in networking slicing.
root@open5gc:/etc/open5gs# tail /var/log/open5gs/nssf.log
06/28 11:53:46.761: [app] INFO: File Logging: '/var/log/open5gs/nssf.log' (../lib/app/ogs-init.c:129)
06/28 11:53:46.763: [app] FATAL: ogs_yaml_iter_key: Assertion `node->type == YAML_SCALAR_NODE' failed. (../lib/app/ogs-yaml.c:135)
06/28 11:53:46.763: [core] FATAL: backtrace() returned 8 addresses (../lib/core/ogs-abort.c:37)
/usr/lib/x86_64-linux-gnu/libogsapp.so.2(ogs_yaml_iter_key+0x108) [0x7f6da85aac08]
/usr/bin/open5gs-nssfd(+0x52aa) [0x555d8c4b02aa]
/usr/bin/open5gs-nssfd(+0x45d5) [0x555d8c4af5d5]
/usr/bin/open5gs-nssfd(+0x410b) [0x555d8c4af10b]
/usr/bin/open5gs-nssfd(+0x3fdd) [0x555d8c4aefdd]
/usr/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f6da7df0083]
/usr/bin/open5gs-nssfd(+0x403e) [0x555d8c4af03e]Config file -
root@open5gc:/etc/open5gs# cat nssf.yaml
#
# o Set OGS_LOG_INFO to all domain level
# - If `level` is omitted, the default level is OGS_LOG_INFO)
# - If `domain` is omitted, the all domain level is set from 'level'
# (Default values are used, so no configuration is required)
#
# o Set OGS_LOG_ERROR to all domain level
# - `level` can be set with none, fatal, error, warn, info, debug, trace
# logger:
# level: error
#
# o Set OGS_LOG_DEBUG to mme/emm domain level
# logger:
# level: debug
# domain: mme,emm
#
# o Set OGS_LOG_TRACE to all domain level
# logger:
# level: trace
# domain: core,sbi,ausf,event,tlv,mem,sock
#
logger:
file: /var/log/open5gs/nssf.log
#
# o TLS enable/disable
# sbi:
# server|client:
# no_tls: false|true
# - false: (Default) Use TLS
# - true: TLS disabled
#
# o Verification enable/disable
# sbi:
# server|client:
# no_verify: false|true
# - false: (Default) Verify the PEER
# - true: Skip the verification step
#
# o Server-side does not use TLS
# sbi:
# server:
# no_tls: true
#
# o Client-side skips the verification step
# sbi:
# client:
# no_verify: true
# key: /etc/open5gs/tls/amf.key
# cert: /etc/open5gs/tls/amf.crt
#
# o Use the specified certificate while verifying the client
# sbi:
# server
# cacert: /etc/open5gs/tls/ca.crt
#
# o Use the specified certificate while verifying the server
# sbi:
# client
# cacert: /etc/open5gs/tls/ca.crt
#
sbi:
server:
no_tls: true
cacert: /etc/open5gs/tls/ca.crt
key: /etc/open5gs/tls/nssf.key
cert: /etc/open5gs/tls/nssf.crt
client:
no_tls: true
cacert: /etc/open5gs/tls/ca.crt
key: /etc/open5gs/tls/nssf.key
cert: /etc/open5gs/tls/nssf.crt
#
# <SBI Server>
#
# o SBI Server(http://<all address available>:80)
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
#
# o SBI Server(http://<any address>:7777)
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# - addr:
# - 0.0.0.0
# - ::0
# port: 7777
#
# o SBI Server(https://<all address available>:443)
# sbi:
# server:
# key: /etc/open5gs/tls/nssf.key
# cert: /etc/open5gs/tls/nssf.crt
# nssf:
# sbi:
#
# o SBI Server(https://127.0.0.14:443, https://[::1]:443) without verification
# sbi:
# server:
# no_verify: true
# key: /etc/open5gs/tls/nssf.key
# cert: /etc/open5gs/tls/nssf.crt
# nssf:
# sbi:
# - addr: 127.0.0.14
# - addr: ::1
#
# o SBI Server(https://nssf.open5gs.org:443)
# Use the specified certificate while verifying the client
#
# sbi:
# server:
# cacert: /etc/open5gs/tls/ca.crt
# key: /etc/open5gs/tls/nssf.key
# cert: /etc/open5gs/tls/nssf.crt
# nssf:
# sbi:
# - name: nssf.open5gs.org
#
# o SBI Server(http://127.0.0.14:7777)
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# - addr: 127.0.0.14
# port: 7777
#
# o SBI Server(http://<eth0 IP address>:80)
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# - dev: eth0
#
# o Provide custom SBI address to be advertised to NRF
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# - dev: eth0
# advertise: open5gs-nssf.svc.local
#
# o Another example of advertising on NRF
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# - addr: localhost
# advertise:
# - 127.0.0.99
# - ::1
#
# o SBI Option (Default)
# - tcp_nodelay : true
# - so_linger.l_onoff : false
#
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# addr: 127.0.0.14
# option:
# tcp_nodelay: false
# so_linger:
# l_onoff: true
# l_linger: 10
#
# <List of available Network Slice Instance(NSI)>
#
# o One NSI
# - NRF[http://::1:7777/nnrf-nfm/v1/nf-instances]
# NSSAI[SST:1]
#
# nssf:
# nsi:
# - addr: ::1
# port: 7777
# s_nssai:
# sst: 1
#
# o Three NSI
# 1. NRF[http://::1:7777/nnrf-nfm/v1/nf-instances]
# S-NSSAI[SST:1]
#
# 2. NRF[http://127.0.0.19:7777/nnrf-nfm/v1/nf-instances]
# NSSAI[SST:1, SD:000080]
#
# 2. NRF[http://127.0.0.10:7777/nnrf-nfm/v1/nf-instances]
# NSSAI[SST:1, SD:009000]
#
# nssf:
# nsi:
# - addr: ::1
# port: 7777
# s_nssai:
# sst: 1
# - addr: 127.0.0.19
# port: 7777
# s_nssai:
# sst: 1
# sd: 000080
# - addr: 127.0.0.10
# port: 7777
# s_nssai:
# sst: 1
# sd: 009000
#
# o NSI Option (Default)
# - tcp_nodelay : true
# - so_linger.l_onoff : false
#
# nssf:
# nsi:
# addr: ::1
# option:
# tcp_nodelay: false
# so_linger:
# l_onoff: true
# l_linger: 10
#
# <NF Service>
#
# o NF Service Name(Default : all NF services available)
# nssf:
# service_name:
#
# o NF Service Name(Only some NF services are available)
# nssf:
# service_name:
# - nnssf-nsselection
#
# <NF Discovery Query Parameter>
#
# o (Default) If you do not set Query Parameter as shown below,
#
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# - addr: 127.0.0.14
# port: 7777
#
# - 'service-names' is included.
#
# o Service-Names are not included
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# - addr: 127.0.0.14
# port: 7777
# discovery:
# option:
# no_service_names: false
#
# o To remove 'service-names' from URI query parameters in NS Discovery
# no_service_names: true
#
# * For Indirect Communication with Delegated Discovery,
# 'service-names' is always included in the URI query parameter.
# * That is, 'no_service_names' has no effect.
#
# <For Indirect Communication with Delegated Discovery>
#
# o (Default) If you do not set Delegated Discovery as shown below,
#
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# - addr: 127.0.0.14
# port: 7777
#
# - Use SCP if SCP avaiable. Otherwise NRF is used.
# => App fails if both NRF and SCP are unavailable.
#
# sbi:
# server:
# no_tls: true
# nssf:
# sbi:
# - addr: 127.0.0.14
# port: 7777
# discovery:
# delegated: auto
#
# o To use SCP always => App fails if no SCP available.
# delegated: yes
#
# o Don't use SCP server => App fails if no NRF available.
# delegated: no
#
nssf:
sbi:
- addr: 127.0.0.14
port: 7777
nsi:
- addr: 127.0.0.10
port: 7777
s_nssai:
- sst: 01
sd: 000001
#
# <SBI Client>>
#
# o SBI Client(http://127.0.1.10:7777)
# sbi:
# client:
# no_tls: true
# scp:
# sbi:
# addr: 127.0.1.10
# port: 7777
#
# o SBI Client(https://127.0.1.10:443, https://[::1]:443) without verification
# sbi:
# client:
# no_verify: true
# key: /etc/open5gs/tls/amf.key
# cert: /etc/open5gs/tls/amf.crt
# scp:
# sbi:
# - addr: 127.0.1.10
# - addr: ::1
#
# o SBI Client(https://scp.open5gs.org:443)
# Use the specified certificate while verifying the server
#
# sbi:
# client:
# cacert: /etc/open5gs/tls/ca.crt
# key: /etc/open5gs/tls/amf.key
# cert: /etc/open5gs/tls/amf.crt
# scp:
# sbi:
# - name: scp.open5gs.org
#
# o SBI Client(http://[fd69:f21d:873c:fb::1]:80)
# If prefer_ipv4 is true, http://127.0.1.10:80 is selected.
#
# sbi:
# client:
# no_tls: true
# scp:
# sbi:
# addr:
# - 127.0.1.10
# - fd69:f21d:873c:fb::1
#
# o SBI Option (Default)
# - tcp_nodelay : true
# - so_linger.l_onoff : false
#
# sbi:
# client:
# no_tls: true
# scp:
# sbi:
# addr: 127.0.1.10
# option:
# tcp_nodelay: false
# so_linger:
# l_onoff: true
# l_linger: 10
#
#
scp:
sbi:
- addr: 127.0.1.10
port: 7777
#
# <SBI Client>>
#
# o SBI Client(http://127.0.0.10:7777)
# sbi:
# client:
# no_tls: true
# nrf:
# sbi:
# addr: 127.0.0.10
# port: 7777
#
# o SBI Client(https://127.0.0.10:443, https://[::1]:443) without verification
# sbi:
# client:
# no_verify: true
# key: /etc/open5gs/tls/amf.key
# cert: /etc/open5gs/tls/amf.crt
# nrf:
# sbi:
# - addr: 127.0.0.10
# - addr: ::1
#
# o SBI Client(https://nrf.open5gs.org:443)
# Use the specified certificate while verifying the server
#
# sbi:
# client:
# cacert: /etc/open5gs/tls/ca.crt
# key: /etc/open5gs/tls/amf.key
# cert: /etc/open5gs/tls/amf.crt
# nrf:
# sbi:
# - name: nrf.open5gs.org
#
# o SBI Client(http://[fd69:f21d:873c:fa::1]:80)
# If prefer_ipv4 is true, http://127.0.0.10:80 is selected.
#
# sbi:
# addr:
# - 127.0.0.10
# - fd69:f21d:873c:fa::1
#
# o SBI Option (Default)
# - tcp_nodelay : true
# - so_linger.l_onoff : false
#
# sbi:
# client:
# no_tls: true
# nrf:
# sbi:
# addr: 127.0.0.10
# option:
# tcp_nodelay: false
# so_linger:
# l_onoff: true
# l_linger: 10
#
#nrf:
# sbi:
# - addr:
# - 127.0.0.10
# - ::1
# port: 7777
#
# o Disable use of IPv4 addresses (only IPv6)
# parameter:
# no_ipv4: true
#
# o Disable use of IPv6 addresses (only IPv4)
# parameter:
# no_ipv6: true
#
# o Prefer IPv4 instead of IPv6 for estabishing new GTP connections.
# parameter:
# prefer_ipv4: true
#
parameter:
#
# o Maximum Number of UE
# max:
# ue: 1024
#
# o Maximum Number of Peer(S1AP/NGAP, DIAMETER, GTP, PFCP or SBI)
# max:
# peer: 64
#
max:
#
# o NF Instance Heartbeat (Default : 0)
# NFs will not send heart-beat timer in NFProfile
# NRF will send heart-beat timer in NFProfile
# (Default values are used, so no configuration is required)
#
# o NF Instance Heartbeat (20 seconds)
# NFs will send heart-beat timer (20 seconds) in NFProfile
# NRF can change heart-beat timer in NFProfile
#
# time:
# nf_instance:
# heartbeat: 20
#
# o Message Wait Duration (Default : 10,000 ms = 10 seconds)
# (Default values are used, so no configuration is required)
#
# o Message Wait Duration (3000 ms)
# time:
# message:
# duration: 3000
time:
Open5GS Release, Revision, or Tag
v2.6.4
Steps to reproduce
I upgraded my version of Open5gs to v2.6.4 today and since the upgrade, I am unable to achieve a stable 5G SA attach of a CPE. The physical gNodeB comes up successfully with the NGInterface in a normal state but the CPE receives a "HTTP response error [400]" during setup. Wireshark trace confirms the initial attach message is sent but no release is seen prior to that. I am using the sample.yaml file to generate the configuration which I have included in the link below.
https://drive.google.com/file/d/1mO7nRNMdMKCGpyFcLgJhfoF4WC-3WGYG/view?usp=sharing
Logs
Expected behaviour
UE should attach with full internet connectivity connectivity
Observed Behaviour
The UE continues to attempt to attach in a loop
eNodeB/gNodeB
Huawei
UE Models and versions
No response