Update guide [Документация VAS Experts]

This is an old revision of the document!


Update guide

Starting from version 12.0, DPI is supported only on centos 8.x and veos.

Preparation for update

  • Make sure that the DPI configuration and dependent services (pcrf, radius) are valid.
  • Check the currently installed version:
    yum info fastdpi
  • If centos 8.x is used, once switch repositories to vault:
    sed -i -e '/^mirrorlist=http:\/\//d' -e 's/^# *baseurl=http:\/\/mirror.centos.org/baseurl=http:\/\/vault.centos.org/' /etc/yum.repos.d/CentOS-*.repo
  • If there are dependency issues or the update cannot be found, run:
    yum clean all

Special operating conditions

For virtual machines, old processors (approximately before 2009), and old amd processors (before ryzen):

Before updating, run:

touch /etc/dpi/noprioadj

In this case, DPI will start with a normal (non-realtime) priority, which reduces cpu (sys) load but may slightly increase latency.

DPI update

  • Main version update:
    yum update fastdpi
  • Installation of a test (beta) version:
    yum --enablerepo vasexperts-beta update fastdpi
If the module yaml error occurs during update, update the module:
dnf upgrade libmodulemd

Service restart

After updating or changing the version, be sure to restart DPI:

service fastdpi restart

If PCRF and/or radius are used, they must also be restarted (only with a valid configuration):

service fastpcrf restart
service fdpi_radius restart

Recommended pcrf restart order:

service fastdpi stop
service fastpcrf restart
service fastdpi start

Operating system update

Do not update the linux kernel version and kernel-dependent utilities.
  • For centos 8.x:
    yum update

Version rollback

  • Example rollback to version 14.0:
    yum downgrade fastdpi-14.0 fastpcrf-14.0 dpiutils-14.0 fastradius-14.0
  • Example rollback to version 12.4:
    yum downgrade fastdpi-12.4-0 fastpcrf-12.4-0

After rollback, service restart is required:

service fastdpi restart

Important notes

  • Customers using bras functionality must take changes into account when upgrading to new versions.
  • Updating the linux kernel may break binary compatibility with kernel abi and cause issues with network driver loading.
  • If the kernel was updated, temporarily configure booting the previous version via grub by setting the required default parameter value in the /etc/grub.conf file.

Was this information helpful?