{{indexmenu_n>2}} ======Update guide====== Starting from version [[dpi:changelog:versions:ver_12|12.0]], DPI is supported **only** on CentOS 8.x and [[veos:installation|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===== Starting with version [[dpi:changelog:versions:ver_14|14.0]], UDR is divided into [[dpi:dpi_components:platform:dpi_admin:admin_db|UDR and SDR]]. The division occurs automatically when the version is updated. * 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 ====Features of updating in a distributed installation==== If the SSG (fastdpi) and PCRF (fastpcrf) modules are installed on different physical or virtual servers, two conditions must be met: - **Uniform software version:**\\ Ensure that the same versions of the fastdpi and fastpcrf packages are installed on both servers. Version mismatches between SSG and PCRF can lead to errors. - **Restart sequence:**\\ Processes must be restarted in the order specified below to restore the connection correctly.\\ Procedure for a distributed scheme: - On the SSG server, stop the DPI service:service fastdpi stop - On the PCRF server, restart the PCRF service:service fastpcrf restart - On the SSG server, start the fastdpi service:service fastdpi start This order ensures that all services are started correctly. =====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 dpiutils-12.4-0 fastradius-12.4-0 After rollback, service restart is required: service fastdpi stop service fastpcrf restart service fastdpi start =====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.