Configuration Guide

PFCP Agent

This document focuses on frequently used configurations. Please refer to upf.json file for the full list of configurable parameters.

These are configurations commonly shared between P4-UPF and BESS-UPF.

Config	Default value	Mandatory	Comments
`log_level`	info	No
`hostname`	-	No	Used to get local IP address and local NodeID in PFCP messages
`http_port`	8080	No
`max_req_retries`	5	No	Max retries for sending PFCP message towards SMF/SPGW-C
`resp_timeout`	2s	No	Period to wait for a response from SMF/SPGW-C
`enable_end_marker`	false	No
`enable_p4rt`	false	Yes for P4-UPF only
`cpiface.enable_ue_ip_alloc`	false	No	Whether to enable UPF-based UE IP allocation
`cpiface.ue_ip_pool`	-	Yes for P4-UPF or when `enable_ue_ip_alloc` is set	IP pool from which we allocate UE IP address
`cpiface.dnn`	-	No	Data Network Name to use during PFCP Association

Config	Default value	Mandatory	Comments
`measure_upf`	false	No	Enable per port metrics
`measure_flow`	false	No	Enable per flow metrics
`access.ifname`	-	Yes	Access-facing network interface name
`core.ifname`	-	Yes	Core-facing network interface name
`enable_notify_bess`	false	No	Whether to enable Notify feature for DDNs

Config	Default value	Mandatory	Comments
`p4rtciface.slice_id`	0	No	Identify P4-UPF slice this PFCP agent instance belongs to
`p4rtciface.access_ip`	-	Yes	N3/S1u address for 5G/4G
`p4rtciface.p4rtc_server`	-	Yes	IP address of the P4Runtime server exposed by UP4
`p4rtciface.p4rtc_port`	-	Yes	TCP port of the P4Runtime server exposed by UP4
`p4rtciface.default_tc`	3	No	Default Traffic Class (default value is ELASTIC - TC=3)
`p4rtciface.clear_state_on_restart`	false	No	Whether to wipe out PFCP state from UP4 datapath on UP4 restart.