VAS Experts documentation dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup

FastPCRF Logs

Anonymous (anonymous@undisclosed.example.com) — 2026-04-30T09:10:09+00:00

FastPCRF Logs Tracing The level of detail in the logs is set by the trace parameter in the /etc/dpi/fastpcrf.conf configuration file. traceverbose1all verbose0 The trace parameter is a bitmask, where each bit enables detailed logging for a specific subsystem:

Authorization Pending Queue

Anonymous (anonymous@undisclosed.example.com) — 2026-04-30T09:10:09+00:00

Authorization Pending Queue FastDPI sends authorization requests to the fastPCRF server, which, in turn, transmits these requests to the RADIUS server. The RADIUS server bandwidth is limited, so fastPCRF has an internal authorization request queue to smooth out peaks of requests.

Persistent queue

Anonymous (anonymous@undisclosed.example.com) — 2026-04-30T09:10:09+00:00

Persistent queue The queue is organized in the file system within the /var/spool/dpi/pcrf directory. An individual file is created for each fastDPI server in this directory using the pq-: name, for example, if there are two fastDPI servers described in fastpcrf.conf:

Full List of Parameters

Anonymous (anonymous@undisclosed.example.com) — 2026-04-30T09:10:09+00:00

Full List of Parameters FastPCRF command line options: * -c - specifies the configuration file name; * -d – run fastPCRF as a daemon; * -h – display help; * -v – print version. Configuration parameters are taken from the

RADIUS Servers Reservation

Anonymous (anonymous@undisclosed.example.com) — 2026-04-30T09:10:09+00:00

RADIUS Servers Reservation Each RADIUS server is described by an FSM (Finite State Machine). A RADIUS server can be in one of six states: * Initial — the state when fastPCRF starts; * Alive — the RADIUS server is accessible, requests can be sent to it;