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
Next revision
Previous revision
en:dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup:fastpcrf_logs [2024/12/05 14:54] elena.krasnobryzhen:dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup:fastpcrf_logs [2025/10/21 07:31] (current) elena.krasnobryzh
Line 1: Line 1:
 +====== FastPCRF Logs ======
 {{indexmenu_n>2}} {{indexmenu_n>2}}
-====== The FastPCRF logs ======+===== Tracing ===== 
 +The level of detail in the logs is set by the ''trace'' parameter in the **''/etc/dpi/fastpcrf.conf''** configuration file. 
 +<note important>The ''trace'' parameter is ignored if the ''[[en:dpi:bras_bng:radius_integration:radius_auth_fastpcrf_setup:radius_auth_fastpcrf_setup_full|verbose]]'' parameter is set to ''1'' — this value enables trace output for **all** subsystems.\\ To configure logging for one specific or several subsystems, the ''verbose'' parameter must be set to ''0''.</note> 
 +The ''trace'' parameter is a bitmask, where each bit enables detailed logging for a specific subsystem: 
 +  * ''0x00000001'' — connection monitor — RADIUS connection monitor. Monitors connection activity and decides to switch to a backup RADIUS server if necessary. 
 +  * ''0x00000002'' — task scheduler — internal task scheduler. 
 +  * ''0x00000010'' — auth server — responsible for receiving authorization requests from fastDPI (fastDPI -> fastPCRF communication). 
 +  * ''0x00000200'' — radius_client connections — detailed logging of Access-Request queries and Access-Accept/Reject responses. 
 +  * ''0x00000400'' — radius_client monitor — logging of Server-Status requests checking RADIUS server liveliness and responses to them. 
 +  * ''0x00001000'' — CoA server — CoA event logging. 
 +  * ''0x00002000'' — CoA listener - creation of connections with CoA clients. 
 +  * ''0x00004000'' — CoA processor - detailed logging of CoA requests. 
 +  * ''0x00010000'' — fdpi_ctl - logging of events for sending data to fastDPI (fastPCRF -> fastDPI communication). 
 +  * ''0x00020000'' — fdpi_crl FIFO - events of the message queue from fastPCRF to fastDPI. CoA requests that need to be sent to all fastDPI servers enter this queue. 
 +  * ''0x00100000'' — logging of start/stop accounting sending. 
 +  * ''0x00200000'' — logging of interim update accounting sending. 
 +  * ''0x00400000'' — logging of receiving raw accounting data from fastDPI.
  
-FastPCRF logs its actions to the /var/log/dpi/ directory.  +<note important>The ''trace'' parameter is hot: its value can be changed on the fly using the ''service fastpcrf reload'' command</note>
-Logs purposes:+
  
-== fastpcrf_alert.log == +FastPCRF logs its actions to the **''/var/log/dpi''** directory.
-The fastPCRF start/halt log. If there are any errors at the start/halt, you will see them in this log.+
  
-== fastpcrf_ap0.log == +Log purposes:
-Log of authorization requests from the fastDPI (fastDPI -> fastPCRF interaction): +
-  * errors occurred when connecting to the fastDPI; +
-  * fastDPI authorization requests traces; +
-  * traces of acounting data received from the fastDPI.+
  
-== fastpcrf_ap1.log ==+===== fastpcrf_alert.log ===== 
 +Log of fastPCRF startup/shutdown. If any errors occurred during startup/stop, you will see them in this log. 
 + 
 +===== fastpcrf_ap0.log ===== 
 +Log of receiving authorization requests from fastDPI (fastDPI -> fastPCRF communication): 
 +  * connection errors with fastDPI; 
 +  * traces of authorization requests received from fastDPI; 
 +  * traces of receiving accounting data from fastDPI. 
 + 
 +===== fastpcrf_ap1.log =====
 CoA log: CoA log:
-  * connections to CoA clients; +  * connections with CoA clients; 
-  * CoA requests receiving and processing+  * receiving and processing CoA requests
 +  * communication with DHCP and DHCPv6 servers when processing ''Framed-Pool'' and ''Framed-IPv6-Pool'' attributes.
  
-== fastpcrf_ap2.log == +===== fastpcrf_ap2.log ===== 
-Interaction with RADIUS-authorization servers: +Interaction with RADIUS authorization servers: 
-  * adding and removing of RADIUS servers; +  * connection and disconnection of RADIUS servers; 
-  * Access-Request authorization requests+  * Access-Request authorization queries
-  * Access-Accept/Reject responses+  * Access-Accept/Reject responses.
  
-== fastpcrf_ap3.log ==+===== fastpcrf_ap3.log =====
 Accounting log: Accounting log:
-  * adding and removing of accounting RADIUS servers; +  * connection and disconnection of RADIUS accounting servers; 
-  * internal accounting database maintenance+  * maintenance of the internal accounting database; 
-  * subscriber accounting start/stop; +  * start/stop of subscriber accounting
-  * sending of of accounting data;+  * sending accounting data.
  
-== fastpcrf_ap4.log == +===== fastpcrf_ap4.log ===== 
-fastPCRF -> fastDPI interaction log+Log of fastPCRF -> fastDPI communication
-  * Connection to fastDPI using the control port; +  * connection with fastDPI via the control port; 
-  * Sending of authorization results to the VAS Experts DPI+  * sending authorization results to SSG
-  * Sending of CoA requests to the VAS Experts DPI.+  * sending CoA requests to SSG.
  
-== fastpcrf_stat.log == +===== fastpcrf_stat.log ===== 
-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 RADIUS and responses received;
   * CoA statistics;   * CoA statistics;
-  * statistics of connection with RADIUS servers and with fastDPI  +  * statistics on connections with RADIUS servers and with fastDPI.
- +
-FastPCRF periodically logs its internal statistics to this log. +
- +
-==  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: +
-  * 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 +
-  * 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 +
-  * 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 +
-  * 0x00002000 - CoA listener - establishing connections to CoA clients +
-  * 0x00004000 - CoA processor - detailed CoA requests logging +
-  * 0x00010000 - fdpi_ctl - logging of events of sending data to the fastDPI  (fastPCRF -> fastDPI interaction) +
-  * 0x00020000 - fdpi_crl FIFO - message queue events (the messages are sent from fastPCRF to fastDPI). CoA-requests being sent to all fastDPI-servers are queued +
-  * 0x00100000 - logging of start/stop accounting sending +
-  * 0x00200000 - logging of interim update accounting sending+
  
-The ''trace'' optons can be used "on the fly": It is allowed to change its value on the fly by the following command: ''service fastpcrf reload'' +FastPCRF periodically dumps its internal statistics into this log.