Configuring the SVM selection algorithm

Light Agents may use an extended SVM selection algorithm, if you use the application under an enterprise license.

You can specify, which SVM selection algorithm Light Agents must use, in one of the following ways:

• In Kaspersky Security Center Administration Console, in Light Agent for Windows policy properties and Light Agent for Linux policy properties.
• In the local interface of Light Agent for Windows.
• Using the Web Console during creating or editing Light Agent for Windows policy and Light Agent for Linux policy (Application settings → Connection to SVM → SVM selection algorithm).

This section describes how to configure the settings using the Administration Console and in Light Agent for Windows local interface.

To specify the SVM selection algorithm to be used by Light Agents in the Administration Console:

1. Open Kaspersky Security Center Administration Console.
2. In the Managed devices folder of the console tree, open the folder with the name of the administration group to which the relevant protected virtual machines belong.
3. In the workspace, select the Policies tab.
4. In the list of policies, select Light Agent for Windows policy to configure Light Agent for Windows settings, or Light Agent for Linux policy to configure Light Agent for Linux settings, and open the Settings: <Policy name> window by double-clicking it.
5. In the policy properties window, select the SVM selection algorithm section in the list on the left.
6. In the right part of the window, select one of the following options:
   • Use the standard SVM selection algorithm

     If this option is selected, Light Agent behavior depends on the type of Kaspersky Security license you use:

     • If you use the application under a standard license, after being installed and started on a virtual machine, Light Agent selects to connect to the SVM that is local for 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, 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 a virtual infrastructure running on OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform, SVM locality is determined in accordance with the OpenStackStandardAlgorithmSvmLocality parameter of 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.

     • If you use the application under an enterprise license, after being installed and started on a virtual machine, Light Agent selects the SVM with lowest number of Light Agent connections regardless of the SVM location in the virtual infrastructure.

     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 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.

7. 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 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 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 SVM is deployed in the same hypervisor cluster as the virtual machine with the installed Light Agent (in a virtual infrastructure running 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 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.

   • Datacenter. 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 Datacenter 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 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 available SVMs in the same data center or in the same availability zone, where the virtual machine with Light Agent is located, then Light Agent does not connect to 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 you selected a custom list of SVM addresses as the method used by Light Agents to discover SVMs, you must set the Ignore SVM path value for the SVM path parameter. If any other value is set, the Light Agents will not be available to connect to SVM.

8. Click the Apply button.
9. 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 this, perform the following actions:
   1. Open the Integration Server configuration file %ProgramFiles(x86)%\Kaspersky VIISLA\viislaservice.exe.config for editing.
   2. 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.
   3. Save the viislaservice.exe.config file.
   4. Restart the Integration Server.

To specify the SVM selection algorithm to be used by the Light Agent in the local interface:

1. Open the application settings window.
2. In the left part of the window, in the Connection to SVM section, select SVM selection algorithm.

   If the settings in the local interface are not available, this means that the values of settings defined by the policy are used for all protected virtual machines of the administration group.

3. Complete steps 6–7 of the previous instructions.
4. To save changes, click the Save button.
5. In a virtual infrastructure running on OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform: if necessary, specify how you want SVM locality determination relative to Light Agent to be determined (see step 9 of the previous instructions).

Page top