| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:dpi:dpi_brief:dpi_requirements [2025/01/29 13:32] – [Table] elena.krasnobryzh | en:dpi:dpi_brief:dpi_requirements [2025/07/01 11:21] (current) – [Table] atereschenko |
|---|
| |
| ===== Minimum Requirements ===== | ===== 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: | 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: |
| |
| <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> | <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> |
| |
| 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. | 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 ONE CPU\\ with a frequency of 2.5 GHz ^ RAM, GB \\ necessary to install memory modules in all processor channels on the motherboard ^ Minimal number \\ of physical ports ^ Number of Public IPs\\ in a NAT pool ^ Packet per second in Million \\ base CPU frequency from 2,5GHz ^ |
| ^ 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 \\ necessary to install memory modules in all processor channels on the motherboard ^ 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 | | | 2 | 1,5 | **SSG-2** | 4 | 12 | 4x1G, 2x10G | 100 | 1M pps | |
| | 4 | 3 | **SSG-4** | 4 | 16 | 6x1G, 2x10G | 500 | 1,5M pps | | | 4 | 3 | **SSG-4** | 4 | 16 | 6x1G, 2x10G | 500 | 1,5M pps | |
| | 10 | 8 | **SSG-10** | 12 | 48 | 2x10G | 2000 | 6M pps | | | 10 | 8 | **SSG-10** | 12 | 48 | 2x10G | 2000 | 6M pps | |
| | 20 | 15 | **SSG-20** | 16 | 64 | 4x10G | 3000 | 9M 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 | | | 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 | |
| | 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 | | | 60 | 50 | **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 | | | 80 | 70 | **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 | 20M pps | | | 100 | 80 | **SSG-100** | 64 [[https://www.amd.com/en/products/cpu/amd-epyc-7702p|AMD 7702P]] | 192 | 20x10G, 8x25G, 8x40G, 4x100G | 7000 | 20M pps | |
| | 120 | 90 | **SSG-120** | 64 [[https://www.amd.com/en/products/cpu/amd-epyc-9534|AMD 9534]] | 256 | 20x10G, 8x25G, 8x40G, 4x100G | 10000 | 22M pps | | | 120 | 100 | **SSG-120** | 64 [[https://www.amd.com/en/products/cpu/amd-epyc-9534|AMD 9534]] | 256 | 20x10G, 8x25G, 8x40G, 4x100G | 10000 | 22M pps | |
| | 160 | 120 | **SSG-160** | 96 [[https://www.amd.com/en/products/cpu/amd-epyc-9654|AMD 9654]] | 384 | 24x10G, 16x25G, 10x40G, 6x100G | 12000 | 30M pps | | | 180 | 160 | **SSG-180** | 96 [[https://www.amd.com/en/products/cpu/amd-epyc-9654|AMD 9654]] | 384 | 24x10G, 16x25G, 10x40G, 6x100G | 12000 | 30M pps | |
| | 240 | 180 | **SSG-240** | 128 [[https://www.amd.com/en/products/cpu/amd-epyc-9754|AMD 9654]] | 512 | 16x25G, 14x40G, 8x100G | 15000 | 45M pps | | | 240 | 200 | **SSG-240** | 128 [[https://www.amd.com/en/products/cpu/amd-epyc-9754|AMD 9754]] | 512 | 16x25G, 14x40G, 8x100G | 15000 | 45M pps | |
| | | 360 | 320 | **SSG-360** | 192 [[https://www.amd.com/en/products/processors/server/epyc/9005-series/amd-epyc-9965.html|AMD 9965]] | 768 | 28x25G, 20x40G, 12x100G | 24000 | 60M pps | |
| <note warning>Important when selecting a server:\\ | <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.\\ | 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.\\ | 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.\\ | 3. **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.\\ |
| 4.**The use of 100G** interfaces is possible only when the platform is delivered through a partner in order to control the server specification.\\ | 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|]]** involves additional internal locks, which reduces system performance to 40G of total traffic, regardless of the number of cores.\\ | 5. **Using the option [[en:dpi:dpi_options:opt_shaping|]]** involves additional internal locks, which reduces system performance to 40G of total traffic per vChannel, 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> | 6. **Every 256 public IP addresses in NAT Pool (/24 subnet) consume 5GB of RAM. /23 = 10GB, /22 = 20GB, /21 = 40GB, /20 = 80GB, /19 = 160GB.** \\ |
| | 7. Depending on the amount of routing information, **an additional 4-8GB of memory will be required for the router (Soft-Router)**. |
| | </note> |
| |
| ===== Requirements for Installation on a Virtual Machine ===== | ===== Requirements for Installation on a Virtual Machine ===== |
| </note> | </note> |
| |
| ===== System requirements for Soft-Router ===== | =====Recommended file system partitioning===== |
| Depending on the amount of routing information, an additional 4-8 GB of memory will be required. | 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 | |
