Configuring the SVM selection algorithm

Support

Support for business applications

Kaspersky Security for Virtualization 6.0 Light Agent

Connecting Light Agents to SVMs

Configuring the SVM selection algorithm

January 25, 2024

ID 254885

You can specify which SVM selection algorithm Light Agents for Linux should use, and configure the settings for using the advanced SVM selection algorithm in the Light Agent policy using the Kaspersky Security Center Administration Console or Kaspersky Security Center Web Console.

Expand all | Collapse all

How to assign an SVM selection algorithm to a Light Agent in Kaspersky Security Center Administration Console

In the Kaspersky Security Center Administration Console tree, in the Managed devices folder, select the administration group containing the virtual machine with the Light Agent whose settings you want to configure.
In the workspace, select the Policies tab.
Select a Kaspersky Endpoint Security policy in the list of policies and double-click to open the Properties: <Policy name> window.
In the policy properties window, select the SVM selection algorithm section in the list on the left.
In the right part of the window, select one of the following options:
- 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.
  
  SVM locality relative to Light Agent is determined depending on the type of virtual infrastructure:
  - 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, an SVM is considered to be local for Light Agent if it is deployed on the same hypervisor as the virtual machine with the installed Light Agent.
  - In the virtual infrastructure running on TIONIX Cloud Platform or OpenStack platform, SVM locality is determined according to the OpenStackStandardAlgorithmSvmLocality parameter in the Integration Server configuration file (%ProgramFiles(x86)%\Kaspersky Lab\Kaspersky VIISLA\viislaservice.exe.config). If default value is used, SVM is considered as local for Light Agent if it is located in the same server group, as the virtual machine with the installed Light Agent.
  If there are no local SVMs for connection, Light Agent selects a SVM with the lowest number of Light Agent connections regardless of SVM path in the virtual infrastructure.
  
  The application does not determine whether the SVM is local relative to the Light Agent if large infrastructure protection mode is enabled for the Protection Server on the SVM. In this case, it is recommended to use the advanced SVM selection algorithm and select the Integration Server as the SVM discovery method.
  
  This option is selected by default.
- Use an advanced SVM selection algorithm
  If this option is selected, with the SVM path slider you can specify how the SVM path in the virtual infrastructure will affect the ‘local’ status of the SVM in relation to the Light Agent. Light Agent can connect only to local SVMs.
  
  You can also specify that SVM path in the virtual infrastructure must not be taken into the account when selecting SVM for connection.
  
  When selecting SVMs, Light Agents consider the number of Light Agents connected to an SVM to ensure that Light Agents are evenly distributed among SVMs available for connection.
If you selected Use an advanced SVM selection algorithm option, and Light Agents use the Integration Server as SVM discovery method, you can specify how SVM path in the virtual infrastructure must be taken into the account when selecting SVM for connection using the SVM path slider.
Allows to specify SVM path type in the virtual infrastructure, which is taken into the account when selecting SVM for connection:
- Hypervisor. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the 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).
  - The 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 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 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 within the same OpenStack project as the virtual machine with the installed Light Agent (in virtual infrastructure running on TIONIX Cloud Platform or OpenStack 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 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 installed Light Agent (in virtual infrastructure running on TIONIX Cloud Platform or 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. Light Agent selects an SVM regardless of its location.
The default selected value is Hypervisor.

The setting is available if the Use an advanced 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, then connecting a Light Agent to this SVM is only possible if the SVM path is ignored (Ignore SVM path is set as the value of the SVM path setting).
Click the Apply button.

How to assign an SVM selection algorithm to a Light Agent in Kaspersky Security Center Web Console

In the main window of Kaspersky Security Center Web Console, select Devices → Policies and policy profiles.
A list of policies opens.
Select the administration group containing the virtual machine with the Light Agent whose settings you want to configure. To do so, click the link in the Current path field located above the list of policies and policy profiles, and select an administration group in the window that opens.
The list displays only the policies configured for the selected administration group.
Click on the name of the Kaspersky Endpoint Security for Linux policy in the list.
In the policy properties window that opens, select the Application settings tab and go to Light Agent mode → SVM selection algorithm.
Select one of the following options:
- 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.
  
  SVM locality relative to Light Agent is determined depending on the type of virtual infrastructure:
  - 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, an SVM is considered to be local for Light Agent if it is deployed on the same hypervisor as the virtual machine with the installed Light Agent.
  - In the virtual infrastructure running on TIONIX Cloud Platform or OpenStack platform, SVM locality is determined according to the OpenStackStandardAlgorithmSvmLocality parameter in the Integration Server configuration file (%ProgramFiles(x86)%\Kaspersky Lab\Kaspersky VIISLA\viislaservice.exe.config). If default value is used, SVM is considered as local for Light Agent if it is located in the same server group, as the virtual machine with the installed Light Agent.
  If there are no local SVMs for connection, Light Agent selects a SVM with the lowest number of Light Agent connections regardless of SVM path in the virtual infrastructure.
  
  The application does not determine whether the SVM is local relative to the Light Agent if large infrastructure protection mode is enabled for the Protection Server on the SVM. In this case, it is recommended to use the advanced SVM selection algorithm and select the Integration Server as the SVM discovery method.
  
  This option is selected by default.
- Use an advanced SVM selection algorithm
  If this option is selected, with the SVM path slider you can specify how the SVM path in the virtual infrastructure will affect the ‘local’ status of the SVM in relation to the Light Agent. Light Agent can connect only to local SVMs.
  
  You can also specify that SVM path in the virtual infrastructure must not be taken into the account when selecting SVM for connection.
  
  When selecting SVMs, Light Agents consider the number of Light Agents connected to an SVM to ensure that Light Agents are evenly distributed among SVMs available for connection.
If you selected Use an advanced SVM selection algorithm option, and Light Agents use the Integration Server as SVM discovery method, you can specify how SVM path in the virtual infrastructure must be taken into the account when selecting SVM for connection using the SVM path slider.
Allows to specify SVM path type in the virtual infrastructure, which is taken into the account when selecting SVM for connection:
- Hypervisor. Light Agent selects for connection a SVM that matches a particular criterion (depending on type of the 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).
  - The 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 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 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 within the same OpenStack project as the virtual machine with the installed Light Agent (in virtual infrastructure running on TIONIX Cloud Platform or OpenStack 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 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 installed Light Agent (in virtual infrastructure running on TIONIX Cloud Platform or 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. Light Agent selects an SVM regardless of its location.
The default selected value is Hypervisor.

The setting is available if the Use an advanced 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, then connecting a Light Agent to this SVM is only possible if the SVM path is ignored (Ignore SVM path is set as the value of the SVM path setting).
Click the Save button.

In virtual infrastructure running on TIONIX Cloud Platform or OpenStack platform, if you selected Use the standard SVM selection algorithm option, you can specify how to determine SVM locality relative to Light Agent. To do this, perform the following actions:

Open the Integration Server configuration file %ProgramFiles(x86)%\Kaspersky VIISLA\viislaservice.exe.config for editing.
Configure value of the OpenStackStandardAlgorithmSvmLocality parameter. This parameter can take the following values:
- Server Group – if this value is selected, SVM is considered local for Light Agent if it is located within the same server group as the virtual machine where Light Agent is installed. This value is used by default.
- Project – if this value is selected, SVM is considered as local for Light Agent if it is deployed within the same OpenStack project, as the virtual machine with the installed Light Agent.
- Availability Zone – if this value is selected, SVM is considered as local for Light Agent, if it is located within the same availability zone, as the virtual machine with the installed Light Agent.
Save the viislaservice.exe.config file.
Restart the Integration Server.

Kaspersky Professional Services

Implementation services. Health check and security system configuration. Contact us if you need expert help.

Kaspersky Premium Support (MSA): High‑priority incident processing

Telephone and web ticket support. Fast response, monitoring and health check. Submit a request and activate the contract (MSA).

Did you find this article helpful?

What can we do better?

Thank you for your feedback! You're helping us improve.