| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:dpi_brief:dpi_requirements:start [2023/08/28 14:34] – elena.krasnobryzh | en:dpi:dpi_brief:dpi_requirements:start [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 |
|---|
| ====== Hardware requirements and performance====== | |
| {{indexmenu_n>1}} | |
| |
| ===== Minimum Requirements ===== | |
| SSG software runs on general purpose computers. However, due to deep code optimization and integration with the hardware, the hardware configuration has to meet some specific requirements: | |
| |
| <note important>The CPU and RAM parameters are determined according to the required bandwidth. We advise you to look through the [[en:dpi:dpi_brief:dpi_requirements#recommended_requirements|Recommended Requirements]] and agree on the choice of software server with VAS EXPERTS's representatives or our partners to install the software.</note> | |
| |
| |CPU |**One CPU** supporting **SSE 4.2** staring from [[http://en.wikipedia.org/wiki/Nehalem_(microarchitecture)|Intel Nehalem]] and [[https://en.wikipedia.org/wiki/Zen_2|AMD EPYC Zen2]] with **4 or more processor cores**, **2.5 Ghz clockspeed** and above**.\\ **!SSG only works with one processor!| | |
| |RAM |Not less than 8Gb, it is recommended to install memory cards in all processor channels on the motherboard| | |
| |SSD Disks |To host the OS and SSG software, it is necessary to use 2 disks with a capacity of 256GB or more, combined in RAID 1 (mirror). It is necessary to use a hardware RAID controller. NVMe SSD disks (in M.2, U.2 form factor or PCI Express expansion cards) are a priority. If the platform does not support this type of media, we recommend using SATA/SAS SSD (DWPD>=1) instead of HDDs| | |
| |Number of network ports|At least **3 ports are required**: **one** for the remote management using SSH (any kind of chipset), **the two** other to process network traffic ([[https://core.dpdk.org/supported/nics/|network cards with DPDK support]])| | |
| |Supported network cards|It is recommended to use **only tested** cards on **Intel** chipsets ((if your card is not included in the list of tested, then software adaptation, additional development and testing will be required)) **with 2, 4 or 6 ports**((We do not provide a specific list of models, as there is a wide choice of manufacturers of these cards: from Intel to Huawei, HP, Dell, Silicom, Advantech, Lanner, Supermicro, Silicom and dozens of others, as well as the motherboard built-in cards or SOC.)):\\ \\ **1GbE interfaces** \\ - e1000 (82540, 82545, 82546)\\ - e1000e (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)\\ - igb (82573, 82576, 82580, I210, I211, I350, I354, DH89xx)\\ - igc (I225)\\ \\ **10GbE interfaces** \\ - ixgbe (82598, 82599, X520, X540, X550)\\ - mlx5\\ \\ **25GbE interfaces** \\ - i40e (XXV710) \\ - mlx5\\ \\ **10GbE and 40GbE interfaces, 40GbE port can handle no more than 30G, it is recommended to use only one port on a dual-port card.** \\ - i40e (X710, XL710, X722, XXV710)\\ \\ **100GbE interfaces, 100GbE port can handle no more than 50G, it is recommended to use only one port on a dual-port card, a motherboard with PCIe 4.0 slots is required** \\ - mlx5 (Mellanox ConnectX-5 Ex)\\ - ice (Intel E810) - we do not recommend it, there are problems in intel firmware on the card: it does not pass GRE tunnels\\ | | |
| |Bypass support |Bypass is supported for Silicom cards [[https://www.silicom-usa.com/pr/server-adapters/networking-bypass-adapters/100-gigabit-ethernet-bypass-networking-server-adapters/p4cg2bpi81-bypass-server-adapter/|100GbE]], [[https://www.silicom-usa.com/pr/server-adapters/networking-bypass-adapters/40-gigabit-ethernet-bypass-networking-server-adapters/pe340g2bpi71-server-adapter/|40GbE]], [[http://www.silicom-usa.com/pr/server-adapters/networking-bypass-adapters/10-gigabit-ethernet-bypass-networking-server-adapters/pe210g2bpi9-ethernet-bypass/|10GbE]] and [[http://www.silicom-usa.com/cats/server-adapters/networking-bypass-adapters/gigabit-ethernet-bypass-networking-server-adapters/|1GbE]]| | |
| |
| <note important>SSG platform operates only under control of the [[en:veos:installation|VEOS (VAS Experts Operating System)]]</note> | |
| |
| ===== Recommended Requirements ===== | |
| |
| Server performance is determined based on peak traffic volume value on the channel. When choosing a CPU, RAM, it is necessary to take into account that the calculation is presented for asymmetric traffic. This means that when installing "in-line" for peak incoming traffic of 12 Gbps (Max IN traffic), you need to purchase a SSG-20 license and a platform with parameters: 1 CPU 16 cores and more, RAM 64GB and more. | |
| <note important>{{ :en:dpi:dpi_components:platform:dpi_requirements:calculator.xlsx |Equipment calculation depending on traffic and functionality}}</note> | |
| ^Total traffic (in+out) \\ Gbps ^Max incoming traffic \\ Gbps^Stingray SG Version ^Number of cores per CPU\\ with a frequency of 2.5 GHz ^RAM \\ GB^Minimal number \\ of physical ports^ Number of Public IPs\\ in a NAT pool^Packet per second in Million \\ base CPU frequency from 2,5GHz^ | |
| |2 |1,5 |**SSG-2** |4 |12 |4x1G, 2x10G |100 |1M pps | | |
| |4 |3 |**SSG-4** |4 |16 |6x1G, 2x10G |500 |1,5M pps | | |
| |6 |5 |**SSG-6** |6 |32 |2x10G |1000 |3-4M pps | | |
| |10 |8 |**SSG-10** |12 |48 |2x10G |2000 |6M pps | | |
| |20 |15 |**SSG-20** |16 |64 |4x10G |3000 |9M pps | | |
| |40 |30 |**SSG-40** |18 [[https://ark.intel.com/content/www/us/en/ark/products/199352/intel-xeon-gold-6242r-processor-35-75m-cache-3-10-ghz.html|Intel 6242R]] |96 |6x10G, 4x25G, 4x40G, 2x100G|4000|12M pps| | |
| |60 |45 |**SSG-60** |28 [[https://ark.intel.com/content/www/us/en/ark/products/199350/intel-xeon-gold-6258r-processor-38-5m-cache-2-70-ghz.html|Intel 6258R]], [[https://ark.intel.com/content/www/us/en/ark/products/215285/intel-xeon-gold-5320-processor-39m-cache-2-20-ghz.html|Intel 5320]], \\ 32 [[https://www.amd.com/en/products/cpu/amd-epyc-7502p|AMD 7502P]] |128 |10x10G, 4x25G, 4x40G, 2x100G|5000|15M pps| | |
| |80 |60 |**SSG-80** |64 [[https://www.amd.com/en/products/cpu/amd-epyc-7702p|AMD 7702P]] |160 |12x10G, 6x25G, 6x40G, 4x100G|6000|18M pps| | |
| |100 |75 |**SSG-100** |64 [[https://www.amd.com/en/products/cpu/amd-epyc-7702p|AMD 7702P]] |192 |20x10G, 8x25G, 8x40G, 4x100G|7000|21M pps| | |
| |120 |90 |**SSG-120** |64 [[https://www.amd.com/en/products/cpu/amd-epyc-9534|AMD 9534]] |256 |20x10G, 8x25G, 8x40G, 4x100G|10000|30M pps| | |
| |160 |120 |**SSG-160** |96 [[https://www.amd.com/en/products/cpu/amd-epyc-9654|AMD 9654]] |512 |24x10G, 16x25G, 10x40G, 6x100G|12000|40M pps| | |
| |160 |180 |**SSG-240** |128 [[https://www.amd.com/en/products/cpu/amd-epyc-9754|AMD 9654]] |512 |16x25G, 10x40G, 8x100G|15000|60M pps| | |
| <note warning>Important when selecting a server:\\ | |
| 1.**The Stingray SG uses only one processor** because of the impact on performance of [[https://en.wikipedia.org/wiki/Non-uniform_memory_access| NUMA]] for dual-processor configurations.\\ | |
| 2.**When choosing a CPU, it is necessary to take into account the base frequency **, the higher the frequency, the greater the performance.\\ | |
| 3.When using **Stingray SG as L2 BRAS (DHCP/ARP/PPPoE authorization)** it is necessary to take into account the additional load associated with the analysis of each packet by additional parameters. This leads to an increase in CPU power consumption. **In such cases it is recommended to increase the number of CPU cores by 30%.** For a SSG-40 license implement the SSG-60 platform.\\ | |
| 4.**The use of 100G** interfaces is possible only when the platform is delivered through a partner in order to control the server specification.\\ | |
| 5.**Using the option [[en:dpi:dpi_options:opt_shaping:start|]]** involves additional internal locks, which reduces system performance to 40G of total traffic, regardless of the number of cores.\\ | |
| 6.**Every 256 public IP addresses in NAT Pool (/24 subnet) consume 5GB of RAM. /22 = 10GB, /21 = 20GB, /20 = 80GB, /19 = 160GB.**</note> | |
| |
| ===== Requirements for Installation on a Virtual Machine ===== | |
| SSG software can be installed on a Virtual Machine (VM). \\ | |
| VM has the following requirements: | |
| * Hypervisor: VMware, KVM | |
| * CPU of at least 4 cores with a frequency of 2.5 GHz | |
| * RAM of 8 Gb and more | |
| * Storage space of 20 Gb and more | |
| |
| Check VM preparation for test: | |
| |
| OS CentOS: **cat /etc/redhat-release** | |
| <code>CentOS Linux release 8.5.2111 (Core)</code> | |
| OS VEOS: **cat /etc/*releas* ** or **cat /etc/system-release** | |
| <code>VEOS release 8.7 (Sakhalin)</code> | |
| \\ \\ | |
| RAM: **cat /proc/meminfo** | |
| <code>MemTotal: 16254744 kB</code> | |
| |
| Checking whether all cores belong to one CPU: **grep "physical id" /proc/cpuinfo |sort -u** | |
| <code>physical id : 0</code> | |
| |
| Number of cores: **grep "cores" /proc/cpuinfo |sort -u** | |
| <code>cpu cores : 4</code> | |
| |
| There must be at least three interfaces (two for traffic and one for administration): **lspci | grep Ethernet** | |
| <code>0b:00.0 Ethernet controller: VMware VMXNET3 Ethernet Controller (rev 01) | |
| 13:00.0 Ethernet controller: VMware VMXNET3 Ethernet Controller (rev 01) | |
| 1b:00.0 Ethernet controller: VMware VMXNET3 Ethernet Controller (rev 01)</code> | |
| |
| <note important>For SSG to work in a virtual environment, in the Security settings of virtual networks in which in_dev and out_dev are composed, you need to enable: | |
| * Promiscuous mode Accept | |
| * MAC address changes Accept | |
| * Forged transmits Accept | |
| </note> | |
| |
| ===== System requirements for Soft-Router ===== | |
| Depending on the amount of routing information, an additional 4-8 GB of memory will be required. | |
