Administration [Документация VAS Experts]
Документация VAS Experts Документация VAS Experts-mobile
in

Settings

  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • ODT export
  • Backlinks
  • Show page
  • Old revisions
  • Export to PDF
  • Fold/unfold all
  • ODT export
  • Backlinks

    • Differences

    This shows you the differences between two versions of the page.

    Link to this comparison view

    Both sides previous revisionPrevious revision
    Next revision    		Previous revision
    en:dpi:dpi_components:radius:radius_admin [2024/09/26 15:29] – external edit 127.0.0.1en:dpi:dpi_components:radius:radius_admin [2026/03/26 08:16] (current) – [Syslog Logging Support] elena.krasnobryzh
    Line 1: Line 1:
     ====== Administration ====== ====== Administration ======
    -{{indexmenu_n>4}} +{{indexmenu_n>3}} 
    -Radius events monitor runs under [[en:veos:installation|VEOS]] or higher. The administration tasks are solved by means that are typical for this OS.+The main process is called ''fdpi_radius''. It is installed as a service in the system and managed using standard service commands.\\ 
     +Restart the service: 
     +<code bash>systemctl fastradius restart</code>
      
    -This chapter depicts peculiarities of monitor's installation and operation that are essential for a system administrator.+FastRADIUS settings are located in the ''/etc/dpi'' directory: 
     +  * ''fdpi_radius.conf'' — configuration file 
     +  * ''prefixes.info'' — region settings (prefixes for subscriber logins), file is absent if not needed
      
    -The main process is named fdpi_radius. It uses CPU resources even in an idle state (no data transmission). This mode is essential to minimize network delays and relates to peculiarities of LAN cards operation. The system treats this process as a service. The latest is controlled by common service commands.+Parameters in the configuration file are either "hot" or "cold":\\ 
     +  * Hot parameters can be changed during operation "on the fly," i.e., without restarting the service. 
     +  * Cold parameters will only take effect after restarting the service.
      
    -For example, to restart the services: +Update hot settings without restarting the service: 
    -<code>service fastradius restart</code>+<code bash>systemctl fastradius reload</code>
      
    -This process is monitored by the system watchdog. It restarts the process in case of abnormal termination. The process has internal self-monitoring means. They support some failure conditions. The process is self terminated in case of critical errors or suspension and then restarted by the watchdog. The latest is configured by the file: ///etc/watchdog.d/wd_fastdpi.sh//.+FastRADIUS logs are located in the ''/var/log/dpi'' directory: 
     +  * ''fdr_alert.log'' — log for informational messages and errors 
     +  * ''fdr_stat.log'' — log for statistical information 
     +Log rotation is handled by the standard ''logrotate'' tool; by default, logs are stored for 24 hours.
      
    -Monitor's configuration parameters are stored in ///etc/dpi//: +The ''logrotate'' configuration file: ''/etc/logrotate.d/fdpi_radius'' \\ 
    -<code> +If the administrator changes the retention period, they must ensure sufficient disk space remains available.
    -fdpi_radius.conf   configuration file +
    -prefixes.info      regional settings (subscribers' login prefixes). The file is omitted if not required +
    -</code>+
      
    -There are "hot" and "cold" configuration file parameters.+Depending on the settings, FastRADIUS may write the following information to the ''/var/dump/dpi'' directory: 
     +  * ''spdu_*.pcap'' - pcap files containing records of bad or all RADIUS packets 
     +  * ''uip_*.txt'' - text logs with information about IP address allocation and release 
     +In this case, it is necessary to implement manual cleanup to prevent disk overflow.
      
    -The "hot" parameters take effect immediately with no need to restart the service. The "cold" parameters require the service to be restarted to become effective.+=====Syslog Logging Support===== 
     +Configured in the ''fdpi_radius.conf'' file
      
    -**For example:** modification of "hot" parameters without restart: +''syslog_level''— the level at which messages from the alert log are written to syslog.
    -<code>service fastradius reload</code>+
      
    -///etc/pf_ring// directory holds licenses for DNA and Libzero. The service runs for 5 minutes only if some of these licenses are missed. +Possible values:  
    - +  * ''0'' — syslog logging is disabled (default value) 
    -Monitor's logs are stored in  ///var/log/dpi//: +  * ''7'' — syslog logging is enabled (7 is the level up to which messages are logged in syslog)
    -<code> +
    -fdr_alert.log messages' and errors' log file +
    -fdr_stat.log  statistics' log file +
    -</code> +
    -Log files' rotation is handled using the standard tool logrotate. The logs are stored for 24 hours by default. The logrotate is configured by the file: ///etc/logrotate.d/fdpi_radius//. +
    - +
    -The available disk space must be checked before modification of logs' storage time by an administrator. +
    - +
    -Depending on its configuration, the Monitor can record to /var/dump/dpi directory the following information: +
    -<code> +
    -spdu_*.pcap - are pcap files containing records of bad or all radius packets +
    -uip_*.txt - are text log files containing information on allocation and release of IP addresses +
    -</code> +
    -One can take care of timely removing of this information to avoid disk space overflow. +
    - +
    -The exact time synchronization runs on the computer via ntpd service. ntpd configuration is stored here: ///etc/sysconfig/ntpd.//+