Kaspersky Security for Virtualization 6.2 Light Agent

Configuring the SVM selection algorithm

You can specify which SVM selection algorithm Light Agents should use, and configure the settings for applying the extended SVM selection algorithm in the Light Agent policy (in the policy of the application running in Light Agent mode). For Light Agent for Windows, you can also select the algorithm in the local interface of Kaspersky Endpoint Security for Windows.

You can choose 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 based 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 that is considered to be local to a Light Agent is the SVM that is deployed on the same hypervisor as the virtual machine with the Light Agent installed.
  • In the virtual infrastructure running on OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform, SVM locality is determined in accordance with the StandardAlgorithmSvmLocality parameter in the HypervisorSpecificSettings:Openstack section of the Integration Server configuration file (appsettings.json). Depending on the version of the Integration Server, the file is located at one of the following paths:
    • /var/opt/kaspersky/viis/common/ for the Linux-based Integration Server
    • %ProgramFiles(x86)%\Kaspersky Lab\Kaspersky VIISLA\ for the Windows-based Integration Server.

  If the 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 extended SVM selection algorithm and select the Integration Server as the SVM discovery method.

  This option is selected by default.

• Use the extended SVM selection algorithm

  If this option is selected, with the SVM path slider you can specify how the SVM location 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 the extended 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

If a Light Agent uses the extended 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 Light Agent ignores the SVM path (the Ignore value is set for the SVM path setting).

For details about configuring the applications running in Light Agent mode, see the Help for the relevant application.

In a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud 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 so, perform the following actions:

1. Open the Integration Server configuration file (appsettings.json) for editing. Depending on the version of the Integration Server, the file is located at one of the following paths:
   • /var/opt/kaspersky/viis/common/ for the Linux-based Integration Server
   • %ProgramFiles(x86)%\Kaspersky Lab\Kaspersky VIISLA\ for the Windows-based Integration Server.
2. Specify the StandardAlgorithmSvmLocality setting in the HypervisorSpecificSettings:Openstack section. This parameter can take the following values:
   • ServerGroup – 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.
   • AvailabilityZone – 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.
3. Save the appsettings.json file.
4. Restart the Integration Server.