Light Agents can apply one of the following SVM selection algorithms for connection:
If this algorithm is applied, 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:
StandardAlgorithmSvmLocality parameter in the HypervisorSpecificSettings:Openstack section of the Integration Server configuration file (%ProgramFiles(x86)%\Kaspersky Lab\Kaspersky VIISLA\appsettings.json).The StandardAlgorithmSvmLocality 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.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.
If this algorithm is applied, you can specify how to determine SVM locality relative to a Light Agent in the Light Agent policy. You can also specify whether Light Agents must consider an SVM's location in the virtual infrastructure when selecting an SVM for connection.
In a virtual infrastructure running on the Microsoft Hyper-V, XenServer, VMware vSphere, KVM, Proxmox VE, Basis (Skala-R), HUAWEI FusionSphere, Nutanix Acropolis, ALT Virtualization Server, Astra Linux, or Numa vServer platform, an SVM is considered to be local for Light Agent in the following cases:
In a virtual infrastructure running on the OpenStack platform, VK Cloud platform, or TIONIX Cloud Platform, an SVM can be considered as local for Light Agent in one of the following cases:
You can select SVM path type, which will be taken into account when determining SVM locality relative to Light Agent. Light Agent can connect only to local SVMs.
For example, if you specify hypervisor cluster as SVM path type, all SVMs deployed on this hypervisor cluster will be considered as local for Light Agent, and Light Agent can connect only to one of this SVMs. If there are no SVMs available for connection in the same cluster in which the Light Agent is running, the Light Agent does not connect to an SVM.
You can also specify that Light Agents must not take into the account SVM path in the virtual infrastructure when selecting an SVM for connection. In this case, Light Agents can connect to any available SVMs.
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.
When selecting an SVM, Light Agents take into account the number of connected Light Agents to ensure that Light Agents are evenly distributed between SVMs that are available for connection.
You can specify which SVM selection algorithm the Light Agents will use, and configure the settings for using the advanced SVM selection algorithm.
Page top