Administration Questions

fastdpi -re
fastdpi -ve
yum downgrade fastdpi-2.6

fdpi_ctrlDPI
/etc/sysctl.conf

# OS network stack optimization net.core.netdev_max_backlog=10000 net.core.somaxconn=262144 net.ipv4.tcp_syncookies=1 net.ipv4.tcp_max_syn_backlog = 262144 net.ipv4.tcp_max_tw_buckets = 720000 net.ipv4.tcp_tw_recycle = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_tw_reuse = 1 net.ipv4.tcp_fin_timeout = 30 net.ipv4.tcp_keepalive_time = 1800 net.ipv4.tcp_keepalive_probes = 7 net.ipv4.tcp_keepalive_intvl = 30 net.core.wmem_max = 33554432 net.core.rmem_max = 33554432 net.core.rmem_default = 8388608 net.core.wmem_default = 4194394 net.ipv4.tcp_rmem = 4096 8388608 16777216 net.ipv4.tcp_wmem = 4096 4194394 16777216
net.core.netdev_max_backlog=10000
net.core.netdev_max_backlog=30000
sysctl -w <setting>
sysctl -w net.ipv4.tcp_tw_reuse=1

For CentOS 7

# OS network stack optimization net.core.netdev_max_backlog=65536 net.core.optmem_max=25165824 net.core.somaxconn=1024 net.ipv4.tcp_max_orphans = 60000 net.ipv4.tcp_no_metrics_save = 1 net.ipv4.tcp_window_scaling = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_sack = 1 net.ipv4.tcp_syncookies=1 net.ipv4.tcp_max_syn_backlog = 262144 net.ipv4.tcp_max_tw_buckets = 720000 net.ipv4.tcp_tw_recycle = 1 net.ipv4.tcp_timestamps = 1 net.ipv4.tcp_tw_reuse = 1 net.ipv4.tcp_fin_timeout = 30 net.ipv4.tcp_keepalive_time = 1800 net.ipv4.tcp_keepalive_probes = 7 net.ipv4.tcp_keepalive_intvl = 30 net.core.wmem_max = 33554432 net.core.rmem_max = 33554432 net.core.rmem_default = 8388608 net.core.wmem_default = 4194394 net.ipv4.tcp_rmem = 4096 8388608 16777216 net.ipv4.tcp_wmem = 4096 4194394 16777216
sysctl –system

More information on CentOS7

Scripts for migrating from SCE SM to SSG database, description inside

top
DPI

ps -p `pidof fastdpi` H -o %cpu,lwp,pri,psr,comm

Example

%CPU LWP PRI PSR COMMAND 0.0 23141 41 0 fastdpi_main 0.0 23146 41 0 fastdpi_dl 0.3 23147 41 0 fastdpi_ctrl 35.8 23148 41 0 fastdpi_ajb 32.7 23152 41 1 fastdpi_rx_1 34.1 23165 41 2 fastdpi_wrk0 34.1 23170 41 3 fastdpi_wrk1

DPI

wrk threads perform data analysis in network packets

rx thread handles data transit between network ports

other threads perform application and auxiliary tasks (generating Netflow, receiving control commands, loading lists, writing PCAP, etc.) and can create peak loads on the CPU, so they are assigned to a separate core.

DPImem_ip_metadata_recs
For example,/etc/dpi/fastdpi.conf

mem_ip_metadata_recs=500000
service fastdpi restart
cp /etc/pf_ring/ /BACKUPDIR/pf_ring cp /etc/dpi /BACKUPDIR/etc/ mdb_copy /var/db/dpi /BACKUPDIR/db/

mdb_copy

echo 100 > /sys/module/ipmi_si/parameters/kipmid_max_busy_us

/etc/rc.local

DPIDPI

Important: trace and dbg settings in fastdpi.conf are intended for diagnostics and debugging, not for permanent operation. If disk write is blocked by another process (e.g., log rotation, which typically occurs from 3 to 4 AM), enabling tracing may cause the working thread to block on writing to the diagnostic (slave) log, leading to DPI switching to bypass or restarting. After diagnostics, remember to disable these settings.
echo deadline > /sys/block/sda/queue/scheduler echo deadline > /sys/block/sdb/queue/scheduler

DPI
mem_preset=1/etc/dpi/fastdpi.confDPI

166206 ? Z 0:00 \_ [wd_fastdpi.sh] <defunct> 166219 ? Z 0:00 \_ [wd_fastpcrf.sh] <defunct>
service watchdog restart

Personal computer

Smartphone on iOS

Smartphone on Android

It is recommended to conduct the test on a PC in incognito mode.

When testing on a smartphone, enable power-saving mode.

Check if the following parameters are enabled in the /etc/dpi/fastdpi.conf file:

trace_ip=“subscriber's IP” ajb_save_ip=“subscriber's IP” plc_trace_ip=“subscriber's IP”

If any of these parameters are enabled, comment them out and perform service fastdpi reload.

Execute the command

find /var/log/dpi -type f -name "fastdpi_slave_*.log" -exec sh -c 'cat /dev/null > {}' \;

The command should clear the fastdpi_slave_*.log files.

Delete all files from /var/dump/dpi/.

Open the /etc/dpi/fastdpi.conf file in a text editor. Add the parameters:

trace_ip=“subscriber's IP” ajb_save_ip=“subscriber's IP” plc_trace_ip=“subscriber's IP” #For this parameter to work, the test subscriber must have a policing profile

Prepare the test subscriber for launch to generate problematic traffic.

Perform service fastdpi reload.

Start generating traffic. Record traffic for 1 minute.

Open the fastdpi.conf file. Comment out the parameters:

trace_ip=“subscriber's IP” ajb_save_ip=“subscriber's IP” plc_trace_ip=“subscriber's IP”

Perform service fastdpi reload.

Prepare the output of the following commands into files:

“fastdpi -ve” “dscp2lst /etc/dpi/protocols.dscp” “fdpi_ctrl list --policing --ip “subscriber's IP” “dscp2as /etc/dpi/asnum.dscp”.

Prepare an archive with the files from point 10 and the fastdpi.conf file.
From /var/log/dpi — fastdpi_stat.log, fastdpi_slave_*.log.
From /var/dump/dpi — udp_*.pcap.

Repeat the required number of tests with different devices. Indicate in the archive name or in a readme.txt file within the archive the types of devices used for testing.

Attach the archives to the ticket. If the archives are too large, upload them to any cloud file sharing service and send us the link.