Kaspersky SD-WAN includes the following main components:
To deploy the Controller, you need to deploy the physical network function of the Controller, which is contained in the installation archive. The Controller is managed by the orchestrator.
If you want a link to be established between two standard CPEs, you need to assign the same topology tag to these standard CPEs. You can also make a standard CPE device a transit device to allow other CPE devices to make links through that CPE device.
If virtual network functions are used, the architecture includes a Virtual Infrastructure Manager (VIM) that manages compute, network, and storage resources within the NFV infrastructure. A VIM connects VNFs using virtual links, subnets, and ports. The OpenStack cloud platform is used as the VIM.
Kaspersky SD-WAN has a distributed microservice architecture based on Docker containers (see the figure below). A Controller can include one, three, or five nodes. Controller nodes are deployed on separate virtual machines, which you can run on different physical servers for fault tolerance. When deploying the solution, you can specify virtual machines on which you want to deploy Controller nodes.
Architecture of Kaspersky SD-WAN
Page top