Differences

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

--- en:dpi:dpi_components:radius:radius_requirements:start [2023/11/29 15:30] – elena.krasnobryzh
+++ en:dpi:dpi_components:radius:radius_requirements:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Description and hardware requirements ======
-{{indexmenu_n>1}}
-Radius events monitor is designed to send to DPI the information on assignment and release of subscribers' IP addresses in networks using dynamic IP assignment((Information transfer on policing services and settings via additional Radius attributes is under development)). It can control DPI servers capable to process a traffic of 100 million subscribers((Radius events monitor is currently in use by Rostelecom network)).
-Radius events monitor runs on a general purpose computer. However, due to deep code optimization and integration with the hardware, the hardware configuration has to meet some specific requirements:
-  - CPU has 2 kernels or more.
-  - Network cards on chipsets Intel 82575/82576/82580/82599 or x540 with 1, 2, 4 or 6 ports.
-  - Any network adapter to handle control connection by SSH (usually the motherboard integrated one is OK).
-Radius events monitor runs under [[en:veos:installation|VEOS]].
-{{ :en:dpi:dpi_components:radius:radius_requirements:radius_en_new.png?900 |}}

Profile