Trouble Shooting
1. ERROR: [SCTP] Failed to connect given AMF N3IWF=NGAP
This error occured when N3IWF was started before AMF finishing initialization. This error usually appears when you run the TestNon3GPP in the first time.
Rerun the test should be fine. If it still not be solved, larger the sleeping time in line 110 of test.sh
.
2. TestNon3GPP
TestNon3GPP will modify the config/amfcfg.conf
. So, if you had killed the TestNon3GPP test before it finished, you might need to copy config/amfcfg.conf.bak
back to config/amfcfg.conf
to let other tests pass.
cp config/amfcfg.conf.bak config/amfcfg.conf
3. DB on TLS to H2C
If you meet any problems about https or mogodb, it maybe couse our new version from v3.0.1 to v3.0.2 has change http to H2C verion. Try the command below.
mongo --eval "db.NfProfile.drop()" free5gc
4. MQCreate() Error creating message queue: Too many open files UPF=Util
(UPF)
Remove POSIX message queues
ls /dev/mqueue/
rm /dev/mqueue/*
5. Remove gtp devices (using tools in libgtp5gnl) (UPF)
cd lib/libgtp5gnl/tools
sudo ./gtp5g-link del {Dev-Name}
6. Decode HTTP/2 packet in Wireshark
-
Run Network Function
Check has XXFsslkey.log
-
Edit » Preference » Protocols » SSL (TLS)
-
Add keylog
-
Filter http2
7. Decode H2C (HTTP2 clear text without TLS)
The similar reason as NEA0 NAS message. Althrough H2C is clear text, wirshark still considers these packets as the normal TCP packets and does not decode them by HTTP2.
To see the details of H2C packets, do the following configuration.
-
Analyze → Decode As…
-
click Add button to add the decode rules
Decode the packets from the TCP ports listened by each NF as HTTP2 packets.