Help with UP4
David Lake
Hello Charles
I need some assistance understanding/configuring UP4 please. The UP4 application is loaded in ONOS and my single EdgeCore switch appears correctly.
However, when I look at the up4 interfaces in ONOS, I see this:
karaf@root up4> read-interfaces
UpfInterface(type=ACCESS, prefix=172.17.0.1/32, slice_id=0)
UpfInterface(type=CORE, prefix=10.250.0.0/24, slice_id=0)
karaf@root up4>
172.17.0.1 is the docker0 interface of the Kubernetes control plane so I don’t see why this given as the N3 address of the UPF?
These values do not match the settings in the netcfg that has been pushed to the switch:
"apps": {
"org.omecproject.up4": {
"up4": {
"devices": [
"device:5g1",
"device:5g2"
],
"n3Addr": "10.0.100.100",
"uePools": [
],
"sliceId": 0,
"pscEncapEnabled": false
}
}
}
My gNB is configured to connect to N3 address 10.0.100.100 – what do I need to change please and how?
Thank you
David
David Lake
Tel: +44 (0)7711 736784
5G & 6G Innovation Centres
Institute for Communication Systems (ICS)
University of Surrey
Guildford
GU2 7XH
Ventre, Pier
+Daniele, Tomasz
Hi David,
This is an unfortunate collision 😊. These are the default config values in the pfcp agent helm chart. Pfcp-agent has the capability to configure those values and IIRC, this will have priority. You can configure directly in the pfpc charts these interface values.
Thanks
Pier
--
You received this message because you are subscribed to the Google Groups "SDFABRIC-Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
sdfabric-dev...@opennetworking.org.
To view this discussion on the web visit
https://groups.google.com/a/opennetworking.org/d/msgid/sdfabric-dev/DBAPR06MB68554CFE08BCE481BD537FA7B5029%40DBAPR06MB6855.eurprd06.prod.outlook.com.
---------------------------------------------------------------------
INTEL CORPORATION ITALIA S.p.A. con unico socio
Sede: Milanofiori Palazzo E 4
CAP 20094 Assago (MI)
Capitale Sociale Euro 104.000,00 interamente versato
Partita I.V.A. e Codice Fiscale 04236760155
Repertorio Economico Amministrativo n. 997124
Registro delle Imprese di Milano nr. 183983/5281/33
Soggetta ad attivita' di direzione e coordinamento di
INTEL CORPORATION, USA
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
David Lake
Hi Pier
Ah! That is a shame… ☹
I don’t want to have to reinstall the entire system – it has taken many weeks to get this all working. Can I just delete the helm chart for the pfcp-agent and reinstall with the correct values?
I’ve found another issue in the pfcp-agent – there is a hostname referenced “pfcp-agent.k8s.intra” but I have these:
root@cp-node:/home/admin5g/sdfabric-helm-charts/pfcp-agent# kubectl -n sdfabric get pods
NAME READY STATUS RESTARTS AGE
sdfabric-atomix-0 1/1 Running 0 67d
sdfabric-onos-classic-0 1/1 Running 0 67d
sdfabric-onos-classic-onos-config-loader-5c9449bd4-vbwjl 0/1 Running 0 67d
sdfabric-pfcp-agent-0 1/1 Running 438 67d
stratum-7rsp6 1/1 Running 0 67d
stratum-xws5q 1/1 Running 1 67d
Do I need to change the hostname in the pfcpagent helm chart as well?
Thank you
(and thank you for the VERY quick reply!)
David
To view this discussion on the web visit https://groups.google.com/a/opennetworking.org/d/msgid/sdfabric-dev/BL0PR11MB30897C900E8A0A64C3203ABAF1029%40BL0PR11MB3089.namprd11.prod.outlook.com.
Ventre, Pier
You may want to check the services deployed in the sdfabric namespace first.
Where is it referenced that hostname ?
To view this discussion on the web visit https://groups.google.com/a/opennetworking.org/d/msgid/sdfabric-dev/DBAPR06MB6855A2F8820C8520A7C667C4B5029%40DBAPR06MB6855.eurprd06.prod.outlook.com.
David Lake
List of services:
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
sdfabric-atomix-api ClusterIP 10.111.53.142 <none> 5678/TCP 67d
sdfabric-atomix-hs ClusterIP None <none> 5679/TCP 67d
sdfabric-onos-classic-hs ClusterIP None <none> 51001/TCP,9876/TCP,8101/TCP,8181/TCP 67d
sdfabric-pfcp-agent ClusterIP 10.109.62.121 <none> 8805/UDP 67d
sdfabric-pfcp-agent-rest ClusterIP 10.111.83.127 <none> 8080/TCP 67d
The name pfcp-agent.k8s.intra is in the Helm chart for the pfcp-agent and when I look at the config file (/tmp/conf/upf.json) that gets loaded into the pfcp agent container it is there as well:
{"cpiface":{"dnn":"internet","hostname":"pfcp-agent.k8s.intra","http_port":"8080","ue_ip_pool":"10.250.0.0/24"},"enable_p4rt":true,"log_level":"info","p4rtciface":{"access_ip":"172.17.0.1/32","p4rtc_port":"51001","p4rtc_server":"sdfabric-onos-classic-hs","slice_id":0}}
The description says that this name is used to look up the IP address in the PFCP messages but that it is ‘optional.’ I have deployed a Free5GC instance but have not tried to connect N4 to the PFCP agent yet…
To view this discussion on the web visit https://groups.google.com/a/opennetworking.org/d/msgid/sdfabric-dev/BL0PR11MB308940F78331A4C226B7DF8DF1029%40BL0PR11MB3089.namprd11.prod.outlook.com.
David Lake
Hello
I was able to delete the 172.17.0.1 ‘ACCESS’ address in ONOS using upf:n3-delete and add my access address of ’10.0.100.100’ using upf:n3-insert.
If I now look at the tables on the EdgeCore switches I see the ‘gtpu=1’ against the target address of 10.0.100.100 (0xa0006464) so I think I may be ready to start generating some GTP packets to see what happens.
I am still a little confused by the lack of the host-name pfcp-agent.k8s.intra …
David
To view this discussion on the web visit https://groups.google.com/a/opennetworking.org/d/msgid/sdfabric-dev/DBAPR06MB6855820057FA4652F02D9997B5029%40DBAPR06MB6855.eurprd06.prod.outlook.com.