SVM selection algorithm

In this window, you can specify which SVM selection algorithm Light Agents for Linux should use, and configure the settings for using the advanced SVM selection algorithm.

Setting	Description
Use the standard SVM selection algorithm	If this option is selected, after installing and running on a virtual machine, the Light Agent selects an SVM to connect to that is local to Light Agent. For more details, refer to the Help for Kaspersky Hybrid Cloud Security for Virtualization Light Agent. If there are no local SVMs available for connection, the Light Agent selects the SVM that has the fewest Light Agents connected, regardless of the location of the SVM in the virtual infrastructure. This option is selected by default.
Use the extended SVM selection algorithm	If this option is selected, you can use the SVM path slider to specify how the SVM's location in the virtual infrastructure will be taken into account when determining whether the SVM is local relative to the Light Agent. The Light Agent will only be able to connect to SVMs that are local. You can also specify that the SVM path in the virtual infrastructure should not be taken into account when selecting an SVM to connect to. When selecting an SVM, Light Agents consider the number of Light Agents connected to the SVM to ensure an even distribution of Light Agents among the SVMs available to connect to.
SVM path	Allows you to specify the type of SVM path in the virtual infrastructure, which is taken into account when selecting SVMs for connection: Hypervisor. The Light Agent selects an SVM to connect to that meets the criteria (depending on the type of virtual infrastructure): The SVM is deployed on the same hypervisor as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the Microsoft Hyper-V®, Citrix Hypervisor, VMware vSphere™, KVM, Proxmox VE, Skala-R, HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, or Astra Linux platform). SVM is located in the same server group, as the virtual machine with the installed Light Agent (in virtual infrastructure running on TIONIX Cloud Platform or OpenStack® platform). If there are no SVMs available for connection on the same hypervisor or in the same Server Group where the virtual machine with the Light Agent is located, the Light Agent does not connect to the SVM. Cluster. The Light Agent selects an SVM to connect to that meets the criteria (depending on the type of virtual infrastructure): The SVM is deployed in the same hypervisor cluster as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, Citrix Hypervisor, VMware vSphere, KVM, Proxmox VE, Scala-R, HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, or Astra Linux); The SVM is deployed in the same OpenStack project as the virtual machine with the Light Agent installed (in a virtual infrastructure managed by the TIONIX Cloud Platform or the OpenStack platform). If there are no SVMs available for connection in the same hypervisor cluster or within the same OpenStack project where the virtual machine with the Light Agent is located, the Light Agent does not connect to the SVM. Data center. The Light Agent selects an SVM to connect to that meets the criteria (depending on the type of virtual infrastructure): The SVM is deployed in the same data center as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, Citrix Hypervisor, VMware vSphere, KVM, Proxmox VE, Scala-R, HUAWEI FusionSphere, Nutanix Acropolis, or ALT Virtualization Server). The SVM is located in the same Availability Zone as the virtual machine with the Light Agent installed (in a virtual infrastructure managed by the TIONIX Cloud Platform or the OpenStack platform). If there are no SVMs available for connection in the same data center or Availability Zone where the virtual machine with the Light Agent is located, the Light Agent does not connect to the SVM. Ignore SVM path. When selecting an SVM, the Light Agent does not consider its location. The Hypervisor option is selected by default. The option is available if the Use the extended SVM selection algorithm option is selected.

Setting

Description

Use the standard SVM selection algorithm

If this option is selected, after installing and running on a virtual machine, the Light Agent selects an SVM to connect to that is local to Light Agent. For more details, refer to the Help for Kaspersky Hybrid Cloud Security for Virtualization Light Agent.

If there are no local SVMs available for connection, the Light Agent selects the SVM that has the fewest Light Agents connected, regardless of the location of the SVM in the virtual infrastructure.

This option is selected by default.

Use the extended SVM selection algorithm

If this option is selected, you can use the SVM path slider to specify how the SVM's location in the virtual infrastructure will be taken into account when determining whether the SVM is local relative to the Light Agent. The Light Agent will only be able to connect to SVMs that are local.

You can also specify that the SVM path in the virtual infrastructure should not be taken into account when selecting an SVM to connect to.

When selecting an SVM, Light Agents consider the number of Light Agents connected to the SVM to ensure an even distribution of Light Agents among the SVMs available to connect to.

SVM path

Allows you to specify the type of SVM path in the virtual infrastructure, which is taken into account when selecting SVMs for connection:

Hypervisor. The Light Agent selects an SVM to connect to that meets the criteria (depending on the type of virtual infrastructure):
- The SVM is deployed on the same hypervisor as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the Microsoft Hyper-V®, Citrix Hypervisor, VMware vSphere™, KVM, Proxmox VE, Skala-R, HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, or Astra Linux platform).
- SVM is located in the same server group, as the virtual machine with the installed Light Agent (in virtual infrastructure running on TIONIX Cloud Platform or OpenStack® platform).
If there are no SVMs available for connection on the same hypervisor or in the same Server Group where the virtual machine with the Light Agent is located, the Light Agent does not connect to the SVM.
Cluster. The Light Agent selects an SVM to connect to that meets the criteria (depending on the type of virtual infrastructure):
- The SVM is deployed in the same hypervisor cluster as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, Citrix Hypervisor, VMware vSphere, KVM, Proxmox VE, Scala-R, HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, or Astra Linux);
- The SVM is deployed in the same OpenStack project as the virtual machine with the Light Agent installed (in a virtual infrastructure managed by the TIONIX Cloud Platform or the OpenStack platform).
If there are no SVMs available for connection in the same hypervisor cluster or within the same OpenStack project where the virtual machine with the Light Agent is located, the Light Agent does not connect to the SVM.
Data center. The Light Agent selects an SVM to connect to that meets the criteria (depending on the type of virtual infrastructure):
- The SVM is deployed in the same data center as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, Citrix Hypervisor, VMware vSphere, KVM, Proxmox VE, Scala-R, HUAWEI FusionSphere, Nutanix Acropolis, or ALT Virtualization Server).
- The SVM is located in the same Availability Zone as the virtual machine with the Light Agent installed (in a virtual infrastructure managed by the TIONIX Cloud Platform or the OpenStack platform).
If there are no SVMs available for connection in the same data center or Availability Zone where the virtual machine with the Light Agent is located, the Light Agent does not connect to the SVM.
Ignore SVM path. When selecting an SVM, the Light Agent does not consider its location.
The Hypervisor option is selected by default.

The option is available if the Use the extended SVM selection algorithm option is selected.

If a Light Agent uses the advanced SVM selection algorithm and a list of SVM addresses is selected as the SVM discovery method, and large infrastructure protection mode is enabled on an SVM (for more information, see the Kaspersky Security for Virtualization Light Agent Help), then connecting a Light Agent to this SVM is only possible if the SVM path is ignored. You need to set the SVM path setting to Ignore SVM path. If any other value is set, Light Agents will not be able to connect to the SVM.

Page top