| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:bras_bng:cli:pcrfctl [2023/08/28 13:40] – ↷ Page moved from en:dpi:bras_bng:cli:start:pcrfctl to en:dpi:bras_bng:cli:pcrfctl elena.krasnobryzh | en:dpi:bras_bng:cli:pcrfctl [2025/09/19 11:34] (current) – elena.krasnobryzh |
|---|
| ====== FastPCRF Management ====== | ====== FastPCRF Management ====== |
| {{indexmenu_n>100}} | {{indexmenu_n>7}} |
| |
| The following are the fastPCRF commands, so you have to specify the fastPCRF address in the -r argument of the fdpi_cli utility. | The following are the fastPCRF commands, so you have to specify the fastPCRF address in the -r argument of the fdpi_cli utility. |
| | |
| | ===== Connection to PCRF ===== |
| | ==== pcrf connect show ==== |
| | Displays the current status and accumulated statistics for connections to PCRF. |
| | <code> |
| | fdpi_cli -r <address> pcrf connect show |
| | </code> |
| | |
| | ==== pcrf connect switch [<pcrf_index>] ==== |
| | Forces connection to the specified PCRF |
| | <code> |
| | fdpi_cli -r <address> pcrf connect switch [<pcrf_index>] |
| | </code> |
| | where ''<pcrf_indxed>'' — the index of the connection line in the ''auth_server'' parameter. If ''<pcrf_indxed>'' is not specified — it defaults to 0. |
| |
| ===== Authorization request queue ===== | ===== Authorization request queue ===== |
| [[dpi:bras_bng:opt_bras_l3:bras_steps:radius_auth_fastpcrf_setup:pending_queue|Authorization request queue]] - is an internal fastPCRF queue, which is designed to smooth out the peaks of calls to the Radius-server. When fastDPI authorization from fastPCRF, it does not take into account the bandwidth of Radius-server. There are parameters in fastpcrf.conf that set the maximum length and time spent in the queue, but sometimes you need to manually clear the queue or view its statistics. | [[dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup:pending_queue|Authorization request queue]] - is an internal fastPCRF queue, which is designed to smooth out the peaks of calls to the Radius-server. When fastDPI authorization from fastPCRF, it does not take into account the bandwidth of Radius-server. There are parameters in fastpcrf.conf that set the maximum length and time spent in the queue, but sometimes you need to manually clear the queue or view its statistics. |
| |
| ==== pcrf auth queue stat ==== | ==== pcrf auth queue stat ==== |
| {{anchor:persist_queue}} | {{anchor:persist_queue}} |
| |
| [[en:dpi:bras_bng:opt_bras_l3:replication:start|Persistent queue]] management commands (fastPCRF response queues for authorization requests) | [[en:dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup:persistent_queue|Persistent queue]] management commands (fastPCRF response queues for authorization requests) |
| |
| ==== pcrf persist queue stat ==== | ==== pcrf persist queue stat ==== |
