Configuring the SVM selection algorithm for Light Agent
The infrastructure of the organization may have multiple deployed SVMs to which Light Agents can connect. To balance the load on the network and resources of the virtual infrastructure, you need to distribute the Light Agents among the SVMs.
Light Agents can apply one of the following SVM selection algorithms for connection:
Standard algorithm (by default)
The standard algorithm involves the following steps:
Light Agent identifies local SVM.
To identify an SVM as local, Light Agent mainly uses the location of the SVM in the virtual infrastructure. If SVMs are located in the same hypervisor as the Light Agent, Light Agent considers such SVMs local. In some virtual infrastructures, you must manually specify local SVMs using a configuration file.
If Light Agent detects multiple local SVMs, Light Agent selects an SVM with the least number of connected Light Agents. If you could not identify local SVMs, Light Agent selects the SVM with the least number of connected Light Agents in the whole virtual infrastructure.
The extended algorithm lets you manually specify local SVM selection criteria or disable local SVM discovery. To do so, you need to select the SVM path in the virtual infrastructure: Hypervisor, Cluster, or Data center. That is, you must select the scope in which the local SVMs is to be discovered. If the Light Agent cannot connect to a local SVM in the configured discovery scope, it stops trying to connect. The extended algorithm also allows disabling local SVMs discovery for the Light Agent. In this case, Light Agent selects SVMs with the least number of connected Light Agents in the entire virtual infrastructure.
Open the Kaspersky Security Center Administration Console.
In the console tree, select Policies.
Select the necessary policy and double-click to open the policy properties.
In the policy window, select Light Agent mode → SVM selection algorithm.
Select the algorithm:
Use the standard SVM selection algorithm. Light Agent selects SVMs, deployed in the same hypervisor.
Use the extended SVM selection algorithm. Light Agent selects SVMs deployed in the selected SVM path type (by default, Hypervisor).
If necessary select SVM path for the extended SVM selection algorithm:
Hypervisor. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the virtual infrastructure):
The SVMs are deployed in the same hypervisor as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer).
The SVM is located in the same server group as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform).
If there are no available SVMs on the same hypervisor or in the same server group, where the virtual machine with Light Agent is located, then Light Agent does not connect to SVM.
Cluster. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the virtual infrastructure):
The SVMs are deployed in the same hypervisor cluster as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer).
The SVMs are deployed in the same OpenStack project as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform).
If there are no available SVMs on the same hypervisor cluster or within the same OpenStack project, where the virtual machine with Light Agent is located, then Light Agent does not connect to SVM.
Data center. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the virtual infrastructure):
The SVMs are deployed in the same data center as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer).
The SVMs are located in the same availability zone as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud 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. Light Agent ignores the SVM path for connecting to the Protection Server. Light Agents takes into account other criteria: tags, the number of Light Agents connected to an SVM, and so on.
In the main window of the Web Console, select Assets (Devices) → Policies & profiles.
Click the name of the Kaspersky Endpoint Security policy.
The policy properties window opens.
Select the Application settings tab.
Go to Light Agent mode → SVM selection algorithm.
Select the algorithm:
Use the standard SVM selection algorithm. Light Agent selects SVMs, deployed in the same hypervisor.
Use the extended SVM selection algorithm. Light Agent selects SVMs deployed in the selected SVM path type (by default, Hypervisor).
If necessary select SVM path for the extended SVM selection algorithm:
Hypervisor. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the virtual infrastructure):
The SVMs are deployed in the same hypervisor as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer).
The SVM is located in the same server group as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform).
If there are no available SVMs on the same hypervisor or in the same server group, where the virtual machine with Light Agent is located, then Light Agent does not connect to SVM.
Cluster. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the virtual infrastructure):
The SVMs are deployed in the same hypervisor cluster as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer).
The SVMs are deployed in the same OpenStack project as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform).
If there are no available SVMs on the same hypervisor cluster or within the same OpenStack project, where the virtual machine with Light Agent is located, then Light Agent does not connect to SVM.
Data center. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the virtual infrastructure):
The SVMs are deployed in the same data center as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer).
The SVMs are located in the same availability zone as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud 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. Light Agent ignores the SVM path for connecting to the Protection Server. Light Agents takes into account other criteria: tags, the number of Light Agents connected to an SVM, and so on.
In the application settings window, under Light Agent mode click the SVM discovery settings tile.
Select the algorithm:
Use the standard SVM selection algorithm. Light Agent selects SVMs, deployed in the same hypervisor.
Use the extended SVM selection algorithm. Light Agent selects SVMs deployed in the selected SVM path type (by default, Hypervisor).
If necessary select SVM path for the extended SVM selection algorithm:
Hypervisor. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the virtual infrastructure):
The SVMs are deployed in the same hypervisor as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer).
The SVM is located in the same server group as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform).
If there are no available SVMs on the same hypervisor or in the same server group, where the virtual machine with Light Agent is located, then Light Agent does not connect to SVM.
Cluster. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the virtual infrastructure):
The SVMs are deployed in the same hypervisor cluster as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer).
The SVMs are deployed in the same OpenStack project as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform).
If there are no available SVMs on the same hypervisor cluster or within the same OpenStack project, where the virtual machine with Light Agent is located, then Light Agent does not connect to SVM.
Data center. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the virtual infrastructure):
The SVMs are deployed in the same data center as the virtual machine with the Light Agent installed (in a virtual infrastructure on Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer).
The SVMs are located in the same availability zone as the virtual machine with the installed Light Agent (in a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud 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. Light Agent ignores the SVM path for connecting to the Protection Server. Light Agents takes into account other criteria: tags, the number of Light Agents connected to an SVM, and so on.
button.