This is an old revision of the document!
5 Options of CoA notifications being sent to the FastDPI servers
Parameter | Format | Default value | Description |
---|---|---|---|
fdpi_server_list | ip_address%dev:port{,ip_address%dev:port}* | is absent | FastDPI servers list. The optional suffix %dev specifies the interface name used for connection with the specified ip address. For example, fdpi_server_list = 92.168.10.12%eth1:29000,10.10.25.99%eth0:29000 . In the example, the connection will be established with 192.168.10.12, port 29000 on the interface eth1 and with 10.10.25.99, port 29000 on the interface eth0. The maximum number of servers in the list is 16. If the FastDPI is withdrawn from service, it must be removed from the list. |
fifo_fsize | bytes | 1048576 | The size of one FIFO file. This parameter should not be more than rlimit_fsize . If the current FIFO file has reached the specified size, the next FIFO file will be created. The number of files created is not limited. For each FastDPI server from the fdpi_server_list list its own sequential queue is created using FIFO files, so if there are irrelevant entries in the fdpi_server_list list it will result in uncontrolled growth of the FIFO queue to this server and, as a result, to a file system overflow. FIFO files are automatically deleted when all the data they contain is sent to the FastDPI server. When FastPCRF is restarted, the FIFO queue from the previous run is not used, so all the data will be lost and the FIFO queue is recreated from scratch. |
fifo_dir | directory | /var/log/dpi | The directory containing the FIFO queue files. |
fifo_file_prefix | string | fastpcrf_fifo_ | FIFO queue file name prefix. |
fifo_leave_bad_file | boolean parameter | 0 | A value of 1 prevents fastpcrf from deleting the FIFO file caused an error. It is used to analyse if something is wrong with the file. |