Kaspersky SD-WAN

Hardware and software requirements

Kaspersky SD-WAN has the following hardware and software requirements:

Hardware requirements depend on the number of CPE devices being managed (see the table below). If you need to connect more than 250 CPE devices, you need to deploy additional controllers. If you need to calculate hardware requirements for a specific deployment scheme more precisely, we recommend contacting Kaspersky Technical Support.

Third-party solution requirements

The following third-party solutions are necessary to deploy the solution:

• The Zabbix monitoring system versions 5.0.26 or 6.0.0. For details, please refer to the official documentation of the Zabbix solution.
• The Docker cloud platform version 1.5 or later for deploying Docker containers of solution components. For details, please refer to the official documentation of the Docker cloud platform.
• The OpenStreetMap service for viewing the transport service topology overlaid on a map. If the infrastructure of your organization does not provide for an Internet connection, you can use offline maps. Offline maps take up additional disk space:
  • The offline map (central-fed-district-latest.osm.pbf) takes up approximately 100 GB.
  • Geocoding data takes up approximately 10 GB.

  For detailed information, please refer to the official documentation of the OpenStreetMap service.

Operating system requirements

The following 64-bit operating systems are supported:

• Ubuntu 20.04 LTS or 22.04 LTS
• Astra Linux 1.7 (security level: "Orel").
• RED OS 8.

Requirements for deployment environments of central components of the solution

The following deployment environments are supported for central components of the solution:

• Bare-metal servers:
  • CPU Intel Xeon E5-2600 v2 or later or an equivalent CPU.
  • IOPS 3000 or later.
• VMWare virtualization environment:
  • Version 7.0 or later.
  • The openvm-tools agent must be installed.
  • IOPS 3000 or later.
• KVM virtualization environment:

  Only the original KVM virtualization environment without additional orchestration tools is supported.

  • Kernel version 5.15 or later.
  • qemu-guest-agent must be installed.
  • The CPU must be in host mode.
  • IOPS 3000 or later.

Requirements for links between nodes of solution components

When deploying Kaspersky SD-WAN, you can deploy multiple nodes of solution components. The following requirements apply to links between nodes of solution components:

• Requirements for links between controller nodes:
  • Bandwidth: 1 Gbps
  • RTT (Round Trip Time): 200 ms
  • Packet loss: 0%
• Requirements for links between MongoDB database nodes:
  • Bandwidth: 1 Gbps
  • RTT: 50 ms
  • Packet loss: 0%
• Requirements for links between Redis database nodes:
  • Bandwidth: 1 Mbps
  • RTT: 50 ms
  • Packet loss: 0%

Browser requirements

The following browsers are supported for managing the orchestrator web interface:

• Google Chrome 100 or later
• Firefox 100 or later
• Microsoft Edge 100 or later
• Opera 90 or later
• Safari 15 or later

Requirements for the data storage system

We recommend using your own data storage system for fault tolerance. The following requirements apply to the data storage system:

• Support for simultaneous read and write from multiple hosts.
• The size of the data storage system depends on the size of the files being stored, but at least 40 GB of available protected space that supports further expansion.
• The bandwidth of the link between the storage system and the orchestrator must be at least 1 Gbps; 10-Gigabit Ethernet or 8-Gigabit FC (Fiber Channel) is recommended.
• At least 250 IOPS, at least 400 is recommended.
• The following types of data storage systems are supported:
  • NFS
  • iSCSI
  • FC
  • CephFS
• The data storage system must be mounted.
• Must stay available if the host restarts.

Administrator device requirements

The administrator device for deploying the solution must satisfy the following requirements:

• Operating system:
  • Ubuntu 20.04 LTS or 22.04 LTS
  • RED OS 8.

  The operating system must support internet access or contain a mounted disk image.

• 4 virtual CPU cores.
• 8 GB of RAM.
• 32 GB of free disk space.
• The name and password of the root account must be the same on the administrator device and the virtual machines on which you want to deploy solution components.

CPE device requirements

The following CPE device models are supported:

• KESR-M1-R-5G-2L-W
• KESR-M2-K-5G-1L-W
• KESR-M2-K-5G-1S
• KESR-M3-K-4G-4S
• KESR-M4-K-2X-1CPU
• KESR-M4-K-8G-4X-1CPU
• KESR-M5-K-8G-4X-2CPU
• KESR-M5-K-8X-2CPU

CPE devices of the KESR model are based on x86 (Intel 80x86) and MIPS (Microprocessor without Interlocked Pipeline Stages) processor architectures.

Kaspersky experts carried out tests to confirm the functionality of CPE devices when providing the L3 VPN service (see the table below). DPI (Deep Packet Inspection) was not used on the tested devices, and traffic encryption was disabled.

For detailed information about the characteristics of CPE devices, please refer to the official page of the solution.

You can deploy uCPE devices on servers with x86 (Intel 80x86) or ARM64 processor architecture.

You can use the vKESR-M1 model as a vCPE device. The following virtualization environments are supported for vCPE devices:

• VMware 7.0 or later
• KVM with kernel version 5.15 or later

  Only the original KVM virtualization environment without additional orchestration tools is supported.

vCPE devices of the vKESR-M1 model have the following specifications:

• CPU: 2x vCPU. We recommend using the Intel(R) Xeon(R) Gold 5318Y CPU.
• Virtual RAM: 512 MB.
• HDD: 1024 MB.