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.
Component |
RAM, GB |
Virtual CPU |
Disk, GB |
IOPS |
50 CPE devices |
||||
Redis replica server |
1 |
2 |
100 |
1000 |
Redis Sentinel system |
1 |
2 |
||
MongoDB database |
2 |
2 |
||
Orchestrator |
4 |
4 |
||
Virtual Network Function Manager (VNFM) |
1 |
2 |
||
Proxy Virtual Network Function Manager (VNFM proxy) |
1 |
2 |
||
Frontend part of the solution |
1 |
2 |
||
Database of the Zabbix monitoring system |
1 |
2 |
500 |
1000 |
Zabbix server |
1 |
2 |
||
Frontend part of the Zabbix monitoring system |
1 |
2 |
||
Zabbix proxy server |
1 |
2 |
||
Syslog server |
1 |
1 |
No value |
No value |
Data storage system |
8 |
8 |
20 |
1000 |
Controller |
8 |
8 |
64 |
1000 |
100 CPE devices |
||||
Redis replica server |
1 |
2 |
100 |
1000 |
Redis Sentinel system |
1 |
2 |
||
MongoDB database |
4 |
4 |
||
Orchestrator |
4 |
4 |
||
Virtual Network Function Manager (VNFM) |
1 |
2 |
||
Proxy Virtual Network Function Manager (VNFM proxy) |
1 |
2 |
||
Frontend part of the solution |
2 |
2 |
||
Database of the Zabbix monitoring system |
1 |
4 |
1000 |
1000 |
Zabbix server |
1 |
2 |
||
Frontend part of the Zabbix monitoring system |
1 |
2 |
||
Zabbix proxy server |
1 |
2 |
||
Syslog server |
1 |
2 |
No value |
No value |
Data storage system |
8 |
8 |
20 |
1000 |
Controller |
8 |
8 |
64 |
1000 |
250 CPE devices |
||||
Redis replica server |
2 |
2 |
100 |
1000 |
Redis Sentinel system |
2 |
2 |
||
MongoDB database |
4 |
4 |
||
Orchestrator |
4 |
6 |
||
Virtual Network Function Manager (VNFM) |
2 |
2 |
||
Proxy Virtual Network Function Manager (VNFM proxy) |
2 |
2 |
||
Frontend part of the solution |
2 |
2 |
||
Database of the Zabbix monitoring system |
2 |
4 |
2500 |
1000 |
Zabbix server |
2 |
4 |
||
Frontend part of the Zabbix monitoring system |
2 |
2 |
||
Zabbix proxy server |
2 |
2 |
||
Syslog server |
2 |
2 |
No value |
No value |
Data storage system |
10 |
8 |
20 |
1000 |
Controller |
16 |
8 |
64 |
1000 |
500 CPE devices |
||||
Redis replica server |
2 |
2 |
100 |
1000 |
Redis Sentinel system |
2 |
2 |
||
MongoDB database |
4 |
6 |
||
Orchestrator |
6 |
6 |
||
Virtual Network Function Manager (VNFM) |
2 |
2 |
||
Proxy Virtual Network Function Manager (VNFM proxy) |
2 |
2 |
||
Frontend part of the solution |
2 |
2 |
||
Database of the Zabbix monitoring system |
2 |
4 |
5000 |
1000 |
Zabbix server |
2 |
4 |
||
Frontend part of the Zabbix monitoring system |
2 |
4 |
||
Zabbix proxy server |
2 |
4 |
||
Syslog server |
2 |
2 |
No value |
No value |
Data storage system |
10 |
8 |
20 |
1000 |
Controller |
32 |
8 |
128 |
1000 |
1000 CPE devices |
||||
Redis replica server |
2 |
4 |
100 |
1000 |
Redis Sentinel system |
2 |
2 |
||
MongoDB database |
6 |
6 |
||
Orchestrator |
8 |
6 |
||
Virtual Network Function Manager (VNFM) |
2 |
2 |
||
Proxy Virtual Network Function Manager (VNFM proxy) |
2 |
2 |
||
Frontend part of the solution |
2 |
2 |
||
Database of the Zabbix monitoring system |
2 |
6 |
1000 |
1000 |
Zabbix server |
2 |
6 |
||
Frontend part of the Zabbix monitoring system |
2 |
4 |
||
Zabbix proxy server |
2 |
4 |
||
Syslog server |
2 |
6 |
No value |
No value |
Data storage system |
12 |
10 |
20 |
1000 |
Controller |
64 |
8 |
256 |
1000 |
2000 CPE devices |
||||
Redis replica server |
4 |
4 |
200 |
2000 |
Redis Sentinel system |
4 |
2 |
||
MongoDB database |
8 |
6 |
||
Orchestrator |
10 |
6 |
||
Virtual Network Function Manager (VNFM) |
4 |
2 |
||
Proxy Virtual Network Function Manager (VNFM proxy) |
4 |
2 |
||
Frontend part of the solution |
4 |
4 |
||
Database of the Zabbix monitoring system |
4 |
6 |
2000 |
2000 |
Zabbix server |
4 |
6 |
||
Frontend part of the Zabbix monitoring system |
4 |
6 |
||
Zabbix proxy server |
4 |
6 |
||
Syslog server |
4 |
6 |
No value |
No value |
Data storage system |
16 |
12 |
20 |
1000 |
Controller |
128 |
8 |
512 |
1000 |
5000 CPE devices |
||||
Redis replica server |
6 |
4 |
500 |
5000 |
Redis Sentinel system |
6 |
2 |
||
MongoDB database |
10 |
6 |
||
Orchestrator |
12 |
6 |
||
Virtual Network Function Manager (VNFM) |
6 |
4 |
||
Proxy Virtual Network Function Manager (VNFM proxy) |
6 |
2 |
||
Frontend part of the solution |
8 |
4 |
||
Database of the Zabbix monitoring system |
6 |
8 |
5000 |
5000 |
Zabbix server |
6 |
8 |
||
Frontend part of the Zabbix monitoring system |
6 |
6 |
||
Zabbix proxy server |
6 |
6 |
||
Syslog server |
6 |
8 |
No value |
No value |
Data storage system |
32 |
16 |
50 |
1000 |
Controller |
320 |
8 |
1280 |
1000 |
10,000 CPE devices |
||||
Redis replica server |
8 |
4 |
1000 |
10,000 |
Redis Sentinel system |
8 |
2 |
||
MongoDB database |
12 |
8 |
||
Orchestrator |
16 |
8 |
||
Virtual Network Function Manager (VNFM) |
8 |
4 |
||
Proxy Virtual Network Function Manager (VNFM proxy) |
8 |
2 |
||
Frontend part of the solution |
8 |
4 |
||
Database of the Zabbix monitoring system |
32 |
8 |
10,000 |
10,000 |
Zabbix server |
16 |
8 |
||
Frontend part of the Zabbix monitoring system |
8 |
8 |
||
Zabbix proxy server |
8 |
8 |
||
Syslog server |
8 |
8 |
No value |
No value |
Data storage system |
64 |
32 |
100 |
1000 |
Controller |
640 |
8 |
2560 |
1000 |
Third-party solution requirements
The following third-party solutions are necessary to deploy the solution:
For detailed information, please refer to the official documentation of the OpenStreetMap service.
Operating system requirements
The following 64-bit operating systems are supported:
Requirements for deployment environments of central components of the solution
The following deployment environments are supported for central components of the solution:
Browser requirements
The following browsers are supported for managing the orchestrator web interface:
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:
Administrator device requirements
The administrator device for deploying the solution must satisfy the following requirements:
The operating system must support internet access or contain a mounted disk image.
CPE device requirements
CPE devices have direct Internet access (DIA) without relaying traffic to the central office. The following CPE devices are supported:
For detailed information about the characteristics of CPE devices, please refer to the official page of the solution.
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.
Model |
Packet size (bytes) |
Bandwidth (Mbps) |
KESR-M1 |
IMIX (417) |
30 |
Large (1300) |
115 |
|
KESR-M2 |
IMIX (417) |
165 |
Large (1300) |
241 |
|
KESR-M3 |
IMIX (417) |
805 |
Large (1300) |
1150 |
|
KESR-M4 |
IMIX (417) |
1430 |
Large (1300) |
2870 |