The FastPCRF logs [Документация VAS Experts]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
en:dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup:fastpcrf_logs [2024/09/26 15:29] – external edit 127.0.0.1en:dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup:fastpcrf_logs [2024/12/05 14:54] (current) elena.krasnobryzh
Line 20: Line 20:
  
 == fastpcrf_ap2.log == == fastpcrf_ap2.log ==
-Interaction with Radius-authorization servers: +Interaction with RADIUS-authorization servers: 
-  * adding and removing of Radius servers;+  * adding and removing of RADIUS servers;
   * Access-Request authorization requests;   * Access-Request authorization requests;
   * Access-Accept/Reject responses   * Access-Accept/Reject responses
Line 27: Line 27:
 == fastpcrf_ap3.log == == fastpcrf_ap3.log ==
 Accounting log: Accounting log:
-  * adding and removing of accounting Radius servers;+  * adding and removing of accounting RADIUS servers;
   * internal accounting database maintenance;   * internal accounting database maintenance;
   * subscriber accounting start/stop;   * subscriber accounting start/stop;
Line 41: Line 41:
 Internal fastPCRF statistics  Internal fastPCRF statistics 
   * memory allocation;   * memory allocation;
-  * number of requests sent to the Radius and corresponding responses received;+  * number of requests sent to the RADIUS and corresponding responses received;
   * CoA statistics;   * CoA statistics;
-  * statistics of connection with Radius servers and with fastDPI +  * statistics of connection with RADIUS servers and with fastDPI 
  
 FastPCRF periodically logs its internal statistics to this log. FastPCRF periodically logs its internal statistics to this log.
Line 49: Line 49:
 ==  Tracing == ==  Tracing ==
 The level of log detail is specified by the ''trace'' option in the fastpcrf.conf configuration file. The ''trace'' option is a bitmask, so each bit specifies the detailed logging of a subsystem: The level of log detail is specified by the ''trace'' option in the fastpcrf.conf configuration file. The ''trace'' option is a bitmask, so each bit specifies the detailed logging of a subsystem:
-  * 0x00000001 - connection monitor. Radius connection monitor. It monitors the connections activity, decides on switching to the backup Radius server if necessary.+  * 0x00000001 - connection monitor. RADIUS connection monitor. It monitors the connections activity, decides on switching to the backup RADIUS server if necessary.
   * 0x00000002 - task scheduler. Internal task scheduler   * 0x00000002 - task scheduler. Internal task scheduler
   * 0x00000010 - auth server is responsible for accepting authorization requests from the fastDPI(fastDPI -> fastPCRF interaction)   * 0x00000010 - auth server is responsible for accepting authorization requests from the fastDPI(fastDPI -> fastPCRF interaction)
   * 0x00000200 - radius_client connections. Detailed Access-Request and Access-Accept/Reject responses logging   * 0x00000200 - radius_client connections. Detailed Access-Request and Access-Accept/Reject responses logging
-  * 0x00000400 - radius_client monitor. Logging of Server-Status requests intended to check the Radius server operates and corresponding responses+  * 0x00000400 - radius_client monitor. Logging of Server-Status requests intended to check the RADIUS server operates and corresponding responses
   * 0x00001000 - CoA server. CoA events logging   * 0x00001000 - CoA server. CoA events logging
   * 0x00002000 - CoA listener - establishing connections to CoA clients   * 0x00002000 - CoA listener - establishing connections to CoA clients