====== Hardware requirements and performance======
{{indexmenu_n>2}}
===== Minimum Requirements =====
SSG software runs on general-purpose x86 servers that are installed in a 19-inch rack and have redundant AC/DC power and cooling fans. Due to the high degree of code optimization and integration with hardware, there are some special requirements:
The CPU and RAM parameters are determined according to the required bandwidth. We advise you to look through the [[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.
| 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 necessary to install memory modules 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]]). The current version of DPDK is 25.11. |
| Supported network cards | It is recommended to use **only tested cards** based on **Intel** chipsets((if your card is not on the list of tested cards, software adaptation, development and additional testing will be required)) with 2, 4 or 6 ports((no specific list of models is provided, as there is a very wide choice of manufacturers of these cards: from Intel itself to branded Huawei, HP, Dell, Silicom, Advantech, Lanner, Supermicro and dozens of others, as well as onboard cards on the motherboard or as part of an SoC)). The most popular models: \\ **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) \\ - i40e (X710, XL710, X722, XXV710)\\ - mlx5 (ConnectX-5, ConnectX-6, ConnectX-6 Dx, ConnectX-6 Lx, ConnectX-7)\\ \\ **25GbE and 40GbE interfaces:** \\ - i40e (X710, XL710, X722, XXV710), ice (E810, E822, E823)\\ - mlx5 (ConnectX-5, ConnectX-6, ConnectX-6 Dx, ConnectX-6 Lx, ConnectX-7)\\ \\ **We recommend selecting a platform for 40G / 100G interfaces through partners.** \\ \\ **100GbE interfaces require a motherboard with PCIe 4.0 x16 support or higher.** The PCIe 4.0 x16 bus supports 256Gbps in each direction, but it is important to pay attention to the performance of 100G network cards. The specifics of Intel and NVIDIA (Mellanox) cards are described below.\\ \\ - ice (Intel E810 (100Gbps: LRES1014PF-2QSFP28, E810-CQDA2) and Intel E830 (200Gbps: E835-CQDA2, LRES1080PF-2QSFP56, E810-2CQDA2))\\ **The LR-Link LRES1014PF-2QSFP28 (2х100GbE) and Intel E810-CQDA2 (2х100GbE) cards**, according to the [[https://fast.dpdk.org/doc/perf/DPDK_25_11_Intel_NIC_performance_report.pdf|Test 3]] report, are guaranteed to process up to 100Gbps of in + out traffic per card in inline or on-stick mode. With [[https://en.wikipedia.org/wiki/Internet_Mix|Internet Mix]], this is 90G download + 10G upload. It is important to consider not only the traffic rate in Gbps but also PPS, since the card chip has different throughput depending on PPS.\\ \\ In **in-line** mode, two ports on the card are used. Port orientation: in (towards subscribers), out (towards the internet).\\ In **on-stick** mode, it is recommended to use only one port on the dual-port 100GbE E810-CQDA2 card, since the total throughput of the card is limited. In on-stick mode, in + out traffic passes through the port twice. \\ \\ **The LR-Link LRES1080PF-2QSFP56 (2х100GbE or 1х200GbE) and Intel E810-2CQDA2 (2х100GbE) cards** have twice the performance and process up to 200Gbps of in + out traffic per card in inline or on-stick mode when both ports are used. **The E810-2CQDA2 card is full-height and larger than the E810-CQDA2, which requires a suitable server chassis.**\\ \\ **- mlx5 (ConnectX-5, ConnectX-6, ConnectX-6 Dx, ConnectX-6 Lx, ConnectX-7)**\\ **The NVIDIA (Mellanox) MCX623106AN-CDAT (2х100GbE) card**, according to the [[https://fast.dpdk.org/doc/perf/DPDK_25_03_NVIDIA_NIC_performance_report.pdf|Test 3]] report, is guaranteed to process up to 200Gbps of in + out traffic per card in inline or on-stick mode. However, it does not support RSS for PPPoE traffic, which is critical for even load balancing across cores. \\ \\ **For BNG PPPoE, only Intel 100G cards must be used (NVIDIA (Mellanox) cards do not support RSS for PPPoE traffic; RSS performs preliminary traffic balancing on the card itself and distributes flows among dispatchers). NVIDIA (Mellanox) cards also have a known issue with processing a single VLAN tag; a potential workaround is to use QinQ. Support for ConnectX-4 and ConnectX-4 Lx has been discontinued in the current DPDK version.** |
| Bypass support | Bypass is supported for [[https://lr-link.com/ru/products/Cyber-Security-Adapters/Bypass-Network-Adapters.html|LR-LINK]] and 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]] |
SSG platform operates only under control of the [[veos:installation|VEOS (VAS Experts Operating System)]]\\ :!: When selecting hardware, take into account the information in [[veos:changelogs]].
===== 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.
^ Total IN+OUT, Gbps ^ Max IN, Gbps ^ SSG Version ^ CPU Cores((Number of cores per CPU\\ with a clock frequency of 2.5 GHz or higher)) ^ RAM, GB((Memory modules must be installed in all CPU memory channels on the motherboard)) ^ Ports((Available port type and quantity options for in-line or on-stick deployment)) ^ Public IP((Number of Public IP addresses\\ in the NAT pool)) ^ PPS((Packets per second, in millions\\ at a CPU base frequency of 2.5 GHz or higher)) ^ Subscribers((Number of subscribers (1 Mbps per subscriber) )) ^ Sessions((Number of sessions)) ^ New Sessions/s((Number of new sessions per second)) ^
| 2 | 1,5 | **SSG-2** | 4 | 12 | 4x1G, 2x10G | 100 | 1M pps | 2K | 2M | 100К |
| 4 | 3 | **SSG-4** | 4 | 16 | 6x1G, 2x10G | 500 | 1,5M pps | 4K | 4M | 100К |
| 6 | 5 | **SSG-6** | 6 | 32 | 2x10G | 1000 | 3-4M pps | 6K | 6M | 200K |
| 10 | 8 | **SSG-10** | 12 | 48 | 2x10G | 2000 | 6M pps | 10K | 12M | 300K |
| 20 | 15 | **SSG-20** | 16 | 64 | 4x10G | 3000 | 9M pps | 20K | 20M | 600K |
| 40 | 35 | **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 | 40K | 40M | 1.2M |
| 80 | 70 | **SSG-80** | 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 | 80K | 80M | 1.3M |
| 160 | 140 | **SSG-160** | 64 [[https://www.amd.com/en/products/cpu/amd-epyc-9534|AMD 9534]], [[https://www.amd.com/en/products/processors/server/epyc/7003-series/amd-epyc-7713.html|AMD 7713]] | 256 | 24x10G, 16x25G, 10x40G, 4x100G | 10000 | 22M pps | 160K | 160M | 1.7M |
| 240 | 210 | **SSG-240** | 96 [[https://www.amd.com/en/products/cpu/amd-epyc-9654|AMD 9654]] | 384 | 24x10G, 16x25G, 10x40G, 6x100G | 12000 | 28M pps | 240K | 240M | 2M |
| 320 | 280 | **SSG-320** | 128 [[https://www.amd.com/en/products/cpu/amd-epyc-9754|AMD 9754]] | 512 | 16x25G, 14x40G, 8x100G | 15000 | 33M pps | 320K | 320M | 2.5M |
| 400 | 350 | **SSG-400** | 160 [[https://www.amd.com/en/products/processors/server/epyc/9005-series/amd-epyc-9845.html|AMD 9845]] | 768 | 24x25G, 16x40G, 10x100G | 20000 | 44M pps | 400K | 400M | 3M |
| 480 | 420 | **SSG-480** | 192 [[https://www.amd.com/en/products/processors/server/epyc/9005-series/amd-epyc-9965.html|AMD 9965]] | 1024 | 28x25G, 10x100G, 10x200G | 24000 | 55M pps | 480K | 480M | 4M |
| 640 | 560 | **SSG-640** | 256 [[https://www.amd.com/en/products/processors/server/epyc/9006-series/amd-epyc-9996.html|AMD 9996]] | 1280 | 10x200G | 30000 | 66M pps | 640K | 640M | 5M |
Important when selecting a server:\\
- **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.
- **When choosing a CPU, it is necessary to take into account the base frequency **, the higher the frequency, the greater the performance.
- **It is recommended to take equipment with a reserve of 20-30% of the planned traffic, in order to prevent congestion during DDoS attacks and the possibility of growth in the future.** For a SSG-40 license implement the SSG-60 platform.
- **The use of 100G** interfaces is possible only when the platform is delivered through a partner in order to control the server specification.
- **Using the [[dpi:dpi_options:opt_shaping:shaping_multi|]] option** and/or **[[dpi:dpi_options:opt_shaping:shaping_settings]]** entails additional internal locks, which reduces system performance to 40G (when using tbf) and to 20G (when using htb) of total traffic on a vChannel or on a shared channel, regardless of the number of cores.
- **Every 256 public IP addresses in NAT Pool (/24 subnet) consume 5GB of RAM. /23 = 10GB, /22 = 20GB, /21 = 40GB, /20 = 80GB, /19 = 160GB.**
- Depending on the amount of routing information, **an additional 4-8GB of memory will be required for the router (Soft-Router)**.
===== 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**
CentOS Linux release 8.5.2111 (Core)
OS VEOS: **cat /etc/*releas* ** or **cat /etc/system-release**
VEOS release 8.7 (Sakhalin)
\\ \\
RAM: **cat /proc/meminfo**
MemTotal: 16254744 kB
Checking whether all cores belong to one CPU: **grep "physical id" /proc/cpuinfo |sort -u**
physical id : 0
Number of cores: **grep "cores" /proc/cpuinfo |sort -u**
cpu cores : 4
There must be at least three interfaces (two for traffic and one for administration): **lspci | grep Ethernet**
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)
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
=====Recommended file system partitioning=====
FS format: ext4
^ Disk type ^ RAID type ^
| 2x960GB SSD SATA | RAID-1 |
^ Mounting point ^ Logical partition size, GB ^ Disc type ^
| ''/boot'' | 1 | 2x960GB SSD - RAID-1 |
| ''/'' | 128 | 2x960GB SSD - RAID-1 |
| ''/SWAP'' | 4 | 2x960GB SSD - RAID-1 |
| ''/var'' | All available | 2x960GB SSD - RAID-1 |