| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:dpi_components:utilities:oldutility:ipfixreceiver [2019/05/14 04:32] – [Creation of systemd ipfixreceiver service in Centos7] kvazikrav | en:dpi:dpi_components:utilities:oldutility:ipfixreceiver [2024/09/26 15:29] (current) – external edit 127.0.0.1 |
|---|
| ==== CentOS6 ==== | ==== CentOS6 ==== |
| |
| - add the VAS Experts repository according to the item 1 of [[en:dpi:dpi_components:platform:dpi_update:dpi_update_10:dpi_10_update:start|DPI installation]] instruction manual. | - add the VAS Experts repository <code>rpm --import http://vasexperts.ru/centos/RPM-GPG-KEY-vasexperts.ru |
| | rpm -Uvh http://vasexperts.ru/centos/6/x86_64/vasexperts-repo-1-0.noarch.rpm</code> |
| - instal the ipfixreceiver:\\ <code>yum install -y ipfixreceiver</code> | - instal the ipfixreceiver:\\ <code>yum install -y ipfixreceiver</code> |
| - check for the changes in the configuration files so they to be consistent with ipfixreceiver current version, see the "Important changes" section. | - check for the changes in the configuration files so they to be consistent with ipfixreceiver current version, see the "Important changes" section. |
| |
| ==== CentOS7 ==== | ==== CentOS7 ==== |
| - add the VAS Experts repository according to the item 1 of [[en:dpi:dpi_components:platform:dpi_update:dpi_update_10:dpi_10_update:start|DPI installation]] instruction manual. | - add the VAS Experts repository <code>rpm --import http://vasexperts.ru/centos/RPM-GPG-KEY-vasexperts.ru |
| | rpm -Uvh http://vasexperts.ru/centos/6/x86_64/vasexperts-repo-1-0.noarch.rpm</code> |
| - install the epel repository <code>yum -y install epel-release</code> | - install the epel repository <code>yum -y install epel-release</code> |
| - install the forencis repository: <code>rpm --import https://forensics.cert.org/forensics.asc | - install the forencis repository: <code>rpm --import https://forensics.cert.org/forensics.asc |
| rpm -Uvh https://forensics.cert.org/cert-forensics-tools-release-el7.rpm</code> | rpm -Uvh https://forensics.cert.org/cert-forensics-tools-release-el7.rpm</code> |
| - установите ipfixreceiver:\\ <code>yum -y install libfixbuf --disablerepo=forensics | - install the ipfixreceiver:\\ <code>yum -y install libfixbuf --disablerepo=forensics |
| yum -y install netsa-python netsa_silk | yum -y install netsa-python netsa_silk |
| yum -y install ipfixreceiver --disablerepo=forensics</code> | yum -y install ipfixreceiver --disablerepo=forensics</code> |
| |
| The field names and their description can be accessed from the following links:\\ | The field names and their description can be accessed from the following links:\\ |
| - [[en:dpi:dpi_options:base_functionality:opt_statistics:statistics_ipfix:start|Netflow export template using the IPFIX format]] | - [[en:dpi:dpi_options:opt_statistics:statistics_ipfix|Netflow export template using the IPFIX format]] |
| - [[en:dpi:dpi_options:base_functionality:opt_li:li_ipfix:start|Clickstream and SIP export templates]] | - [[en:dpi:dpi_options:opt_li:li_ipfix|Clickstream and SIP export templates]] |
| - [[en:dpi:dpi_components:radius:radmon_acct_ipfix:start|AAA export template using the IPFIX format]] | - [[en:dpi:dpi_components:radius:radmon_acct_ipfix|AAA export template using the IPFIX format]] |
| |
| |
| Check whether the service is running: | Check whether the service is running: |
| systemctl status ipfix1.service -l | systemctl status ipfix1.service -l |
| :!: **do not forget to check the service status after rebooting** | :!: **Do not forget to check the service status after rebooting!** |
| |
| ===== Troubleshooting ===== | ===== Troubleshooting ===== |
| - Is it allowed to send IPFIX flows from different DPI to one port?\\ Yes, it is. The only thing is that they can not be distinguished in the recorded flow. | - Is it allowed to send IPFIX flows from different DPI to one port?\\ Yes, it is. The only thing is that they can not be distinguished in the recorded flow. |
| - How can I understand that the utility works properly?\\ a) check that the port specified in the configuration file is listened on by the utility, for example 1500:<code>netstat -nlp | grep 1500</code> b) check the log for errors\\ c) check that the writing to the temporary file occurs, for example for port 9996 (directory for dump files: /var/dump/dpiui/ipfixurl): <code>tail -f /var/dump/dpiui/ipfixurl/9996.url.dump</code> | - How can I understand that the utility works properly?\\ a) check that the port specified in the configuration file is listened on by the utility, for example 1500:<code>netstat -nlp | grep 1500</code> b) check the log for errors\\ c) check that the writing to the temporary file occurs, for example for port 9996 (directory for dump files: /var/dump/dpiui/ipfixurl): <code>tail -f /var/dump/dpiui/ipfixurl/9996.url.dump</code> |
| - everything is checked, but the messages are not receiving?\\ a) it seems you have forgotten to open port in iptables\\ b) it seems you have initialized ipfixreceiver with the wrong server IP. | - everything is checked, but the messages are not received?\\ a) it seems you have forgotten to open port in iptables\\ b) it seems you have initialized ipfixreceiver with the wrong server IP. |
| - a huge number of sessions (more than 2 million sessions/min) is going from the DPI, with DEBUG mode is on, it can be seen that the buffer exchange counter does not have time to write before receiving the next block of records, what can be done in this case?\\ a) remove the date-to-line conversion, this will reduce the time needed for processing and in addition you will receive reduction the size of resulting file\\ b) removing the decodeipv4 conversion will not affect significantly, but you can get the higher speed of writing the file\\ c) configure the ''buffer_size'' when number of sessions per second is more than 30k along with the following item d)\\ d) increase the processor frequency and RAM | - a huge number of sessions (more than 2 million sessions/min) is going from the DPI, it can be seen with the DEBUG mode on that the buffer exchange counter does not have time to write before receiving the next block of records, what can be done in this case?\\ a) remove the date-to-line conversion, this will reduce the time needed for processing and in addition you will receive reduction the size of resulting file\\ b) remove the decodeipv4 conversion; it will not affect significantly, but you can get the higher speed of writing the file\\ c) configure the ''buffer_size'' when number of sessions per second is more than 30k along with the following item d)\\ d) increase the processor frequency and RAM |
