Recommendations for Updating to Beta Version, Configuration, and Log Collection
1. Update the service to the beta version using the command:
yum --enablerepo vasexperts-beta update fastdpi
If you are using BNG functionality and FastPCRF is located on a separate server, execute the following command on the FastPCRF server to update:
yum --enablerepo vasexperts-beta update fastpcrf
Release date 16.02. If the new version is not visible, clear the cache:
yum clean all
2. In the configuration file /etc/dpi/fastdpi.conf, set the following parameter values:
nat_whp_max_viewq=1 nat_dstaddr_cache_size=0
nat_whp_max_viewq - changes the translation view depth
nat_dstaddr_cache_size - disables sending postNATport in IPFIX, optional as it affects NAT translation export
Optionally, if there is a shortage of connection ports
nat_whp_lifetime=10 - sets the short queue time in seconds for NAT translation for TCP SYN, TCP FIN, UDP. This parameter overrides lifetime_flow only for NAT translations. After this time, the port may be reused, but only when the queue for that port on a specific public IP address is reached. Helps reduce port release time.
nat_gcache_slice_k100=150 - changes the port allocation logic, use only if the Private to Public density is low (less than 10:1)
3. Restart SSG. Note that if FastPCRF is on a separate server, restart the fastpcrf service on the FastPCRF server. Restart will interrupt subscriber traffic processing.
Restart SSG in the following order:
service fastdpi stop service fastpcrf restart service fastdpi start
4. Collect a flow dump using the command:
mkdir -p /var/log/dpi/$(date +%Y%m%d) && fdpi_cli dump flow cache > /var/log/dpi/$(date +%Y%m%d)/2_flow.txt
5. Backup fastdpi logs using the command:
tar -jcvf /var/log/dpi/BACKUPLOG_$(date +"%Y%m%d").tar.bz2 /var/log/dpi/fastdpi_*.log /var/log/dpi/fastpcrf_*.log
6. Collect statistics for all subscribers with CG-NAT using the command:
fdpi_ctrl list all status --service 11 > /var/log/dpi/$(date +%Y%m%d)/all_nat.txt
7. Collect statistics for subscribers with more than 800 TCP sessions:
fdpi_ctrl list all status --service 11 | grep -E '^[0-9]' | awk '{for(i=1;i<=NF;i++) if($i ~ /active_sess_tcp=/) {split($i,a,"="); if(a[2]+0 > 800) print}}' > /var/log/dpi/$(date +%Y%m%d)/subscriber_with_T800_nat.txt
8. Collect statistics for subscribers with more than 800 UDP sessions:
fdpi_ctrl list all status --service 11 | grep -E '^[0-9]' | awk '{for(i=1;i<=NF;i++) if($i ~ /active_sess_udp=/) {split($i,a,"="); if(a[2]+0 > 800) print}}' > /var/log/dpi/$(date +%Y%m%d)/subscriber_with_U800_nat.txt
9. Record the outputs of the following commands:
ll -h /var/lib/dpi/proto* ll -h /etc/dpi/as*
10. Notify us so we can download the archive with logs and flow dump from the server. You can also download them yourself and send via any convenient file-sharing service.
Was this information helpful?