This step is displayed if you are deploying an SVM 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.
For this step, you must specify deployment options for each SVM to be deployed on the selected hypervisors. The Hypervisor column displays the IP address in IPv4 format or the fully qualified domain name (FQDN) of the hypervisor on which the SVM will be deployed.
Specify the following settings required for SVM deployment:
The drop-down list displays the storage repositories available for SVM deployment.
If you are deploying SVMs on a Microsoft Windows Server (Hyper-V) hypervisor that is part of a cluster, only shared repositories can be selected in the list.
If you are deploying SVMs on a Microsoft Windows Server (Hyper-V) hypervisor that is not part of a cluster, you can manually enter the path to the repository.
The name of the virtual network that the SVM will use to connect to Light Agents, the Integration Server and the Kaspersky Security Center Administration Server.
You can specify one or more virtual networks available on the hypervisor. To add or remove a field for selecting virtual networks, use the buttons next to the network selection field.
If you intend to use dynamic IP addressing (DHCP) for all SVMs, the network settings will be received from the DHCP server via the first virtual network in the list of networks specified for each SVM. Make sure that the Wizard can connect to the SVM with the network settings of the first virtual network received from the DHCP server.
If the virtual infrastructure uses the VMware Distributed Virtual Switch component, you can specify a Distributed Virtual Port Group to which the SVM will be connected.
If you are deploying an SVM in a virtual infrastructure running the Microsoft Hyper-V platform, you can also specify the VLAN ID.
The ID of the virtual local area network (VLAN) that the SVM will use to connect to Light Agents, the Integration Server and the Kaspersky Security Center Administration Server.