4 FastPCRF journals [Документация 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:service:brass:opt_bras:reference_bras:log_fastpcrf:start [2018/09/30 20:10] kvazikraven:service:brass:opt_bras:reference_bras:log_fastpcrf:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
Line 1: Line 1:
-====== 4 FastPCRF journals ====== 
-{{indexmenu_n>4}} 
  
-=== Log files === 
-FastPCRF logs its actions to the /var/log/dpi/ directory. The following list of log files along with other journals is available: 
-  * [[en:service:brass:opt_bras:reference_bras:log_fastpcrf:fastpcrf_alert|fastpcrf_alert.log]] 
-  * [[en:service:brass:opt_bras:reference_bras:log_fastpcrf:fastpcrf_ap0|fastpcrf_ap0.log]] 
-  * [[en:service:brass:opt_bras:reference_bras:log_fastpcrf:fastpcrf_ap1|fastpcrf_ap1.log]] 
-  * [[en:service:brass:opt_bras:reference_bras:log_fastpcrf:fastpcrf_ap2|fastpcrf_ap2.log]] 
-  * [[en:service:brass:opt_bras:reference_bras:log_fastpcrf:fastpcrf_ap3|fastpcrf_ap3.log]] 
-  * [[en:service:brass:opt_bras:reference_bras:log_fastpcrf:fastpcrf_ap4|fastpcrf_ap4.log]] 
-  * [[en:service:brass:opt_bras:reference_bras:log_fastpcrf:fastpcrf_stat|fastpcrf_stat.lo]] 
- 
-=== Tracking === 
-<note>It is possible to change the tracing parameter values "on the fly", i.e. without stopping the service, by editing the tracing parameter in the fastpcrf.conf configuration file and executing the ''service fastpcrf reload'' command.</note> 
-Logging level is specified by the ''trace'' parameter in the fastpcrf.conf configuration file. The ''trace'' value is specified by bitmask and each its bit specifies the verbose logging of one of the following subsystems: 
- 
-  * 0x00000001 - connection monitor. Radius connection monitor. It monitors the activity of connections, makes the decision to switch to the backup Radius server if necessary. 
-  * 0x00000002 - task scheduler. Internal task scheduler. 
-  * 0x00000010 - auth server, is responsible for authorization requests receiving from the fastDPI(fastDPI → fastPCRF connection). 
-  * 0x00000200 - radius_client connections. Verbose logging of Access-Request requests and corresponding Access-Accept/Reject responses. 
-  * 0x00000400 - radius_client monitor. Logging of the Server-Status requests  being sent to check if the Radius server operates along with logging corresponding responses to them. 
-  * 0x00001000 - CoA server. CoA events logging. 
-  * 0x00002000 - CoA listener - establishing connections with CoA clients. 
-  * 0x00004000 - CoA processor - verbose logging of CoA requests. 
-  * 0x00010000 - fdpi_ctl - logging of the fastDPI data sending events (fastPCRF →fastDPI connection). 
-  * 0x00020000 - fdpi_crl FIFO - message queue events from the fastPCRF to the fastDPI. CoA-requests, which should be sent to all the fastDPI-servers, are placed in the queue. 
-  * 0x00100000 - logging of sending start/stop accounting events. 
-  * 0x00200000 - logging of sending interim update accounting events.