Selecting hypervisors for SVM deployment

At this step, select the hypervisors on which you want to deploy the SVM.

Protection of the virtual infrastructure on the Nutanix Acropolis platform is supported only in the following Kaspersky Security updates: 5.1.1, 5.1.2, and 5.1.3.

If no SVM had been previously deployed on hypervisors in your virtual infrastructure, the list of hypervisors is empty. If SVMs are already deployed on hypervisors in your virtual infrastructure, the table shows a list of these hypervisors and SVMs deployed on them. You can add to the list those hypervisors on which you want to deploy SVMs.

To add hypervisors to the list:

  1. Click the Add button.

    The Virtual infrastructure connection settings window opens.

  2. Specify the following settings for connecting the SVM Management Wizard to hypervisors on which you want to deploy SVMs or the settings for connecting to the virtual infrastructure administration server that controls the hypervisors:
    • The type of hypervisor or virtual infrastructure administration server.
    • Addresses of hypervisors or the address of the virtual infrastructure administration server that controls the hypervisors.

      You can specify an IP address in IPv4 format or a fully qualified domain name (FQDN) as the address of the hypervisor or virtual infrastructure administration server. You can separate the IP addresses or fully qualified domain names of hypervisors by using either a semicolon, a space, or a new line.

      You can also specify the port used for connecting to the hypervisor or to the virtual infrastructure administration server in the format <IP address>:<port>.

      If you are installing the application on Microsoft Windows Server (Hyper-V) hypervisors that are part of a cluster of hypervisors managed by the Windows Failover Clustering service, you can specify the address of any cluster node. All hypervisors that are part of the cluster will be added to the list.

      If you are installing the application on VMware ESXi hypervisors managed by VMware vCenter servers running in Linked mode, you can specify the address of any of these VMware vCenter servers. All the hypervisors running under the management of VMware vCenter servers in Linked mode will be added to the list.

      If you are installing the application on hypervisors that are managed by Microsoft SCVMM, you can specify the settings for connecting to Microsoft SCVMM. All hypervisors that are managed by Microsoft SCVMM will be added to the list.

      The number of correctly recognized addresses is shown under the list of addresses.

    • The name and password of the account used to connect the wizard to the hypervisor or to the virtual infrastructure administration server. This account must have administrator privileges.

      If you use a domain account to connect to a hypervisor or virtual infrastructure administration server, you can specify the account name in the <domain>\<user name> or <user name>@<domain> format.

  3. If you deploy an SVM on a VMware ESXi, Citrix XenServer, KVM, Proxmox VE, R-Virtualization, HUAWEI FusionCompute CNA, or Nutanix AHV hypervisor, you are advised to use an account that has read-only rights to connect the Integration Server to the virtual infrastructure while the application is running. Select the An account with read-only permissions check box and specify the name and password of the account that the Integration Server will use to connect to the virtual infrastructure.

    If the check box is cleared, the Integration Server uses an account with administrator privileges to connect to the virtual infrastructure.

    If you deploy an SVM on a Microsoft Windows Server (Hyper-V) hypervisor, only an account with administrator rights can be used to connect the Integration Server to the virtual infrastructure.

  4. Click the Connect button.

    The Virtual infrastructure connection settings window closes. The Wizard adds the selected hypervisors and/or virtual infrastructure administration servers to the list and attempts to establish a connection.

    The Wizard verifies the authenticity of all hypervisors and virtual infrastructure administration servers with which a connection is being established, except a Microsoft Windows Server (Hyper-V) hypervisor. Authenticity verification is not performed for a Microsoft Windows Server (Hyper-V) hypervisor.

    To verify authenticity, the Wizard receives an SSL certificate or fingerprint of the public key from each hypervisor or virtual infrastructure administration server and verifies them.

    If the authenticity of the received certificate could not be established, the Certificate verification window opens with a message about this. Click the link in this window to view the details of the received certificate. If the certificate complies with the security policy of your organization, you can confirm the authenticity of the certificate and continue connecting to the hypervisor or to the virtual infrastructure administration server. To do so, click the Consider certificate to be authentic button. The received certificate will be installed as a trusted certificate on the computer where the Kaspersky Security Center Administration Console is installed. If you do not consider this certificate to be authentic, click the Cancel button in the Certificate verification window to disconnect, and replace the certificate with a new one.

    If the authenticity of the open key could not be established, the Open key fingerprint verification window opens with a message about this. If you want to confirm the authenticity of the public key and continue connecting to the hypervisor, click the Consider the open key to be authentic button. The open key fingerprint will be saved on the computer where the Kaspersky Security Center Administration Console is installed. If you do not consider this open key to be authentic, click the Cancel button in the Open key fingerprint verification window to terminate the connection.

    If a connection could not be established with a hypervisor or virtual infrastructure administration server, information about the connection errors is displayed in the table.

The table shows the following information about hypervisors and SVMs previously deployed on hypervisors:

You can search for a hypervisor or virtual infrastructure administration server in the list. The search is performed based on the value of the Name column. The search starts as you enter characters in the Search field. The table displays only those hypervisors and virtual infrastructure administration servers that meet the conditions of the search. To reset the search results, delete the contents of the Search field.

You can use the Refresh button above the list to update the list of hypervisors in the table. The SSL certificates of hypervisors and virtual infrastructure administration servers are checked just as when adding a hypervisor or virtual infrastructure administration server to the list.

You can use buttons in the Name column to:

To select hypervisors for SVM deployment:

  1. In the table, select check boxes to the left of the names of hypervisors on which you want to deploy an SVM.

    You can select hypervisors that are not subject to SVM deployment restrictions.

    The simultaneous deployment of SVMs on Nutanix AHV hypervisors and on other types of hypervisors is not supported. You can select either Nutanix AHV hypervisors or the other hypervisor types.

  2. To allow parallel deployment of SVMs on several hypervisors, select the Allow parallel deployment on N hypervisors check box.

Proceed to the next step of the wizard.

Page top