Changing the settings for connection of the Integration Server to the virtual infrastructure

January 10, 2024

ID 73783

To change the settings for connecting the Integration Server to the virtual infrastructure:

  1. Start the Integration Server Console.
  2. In the list on the left, select the Infrastructure connection settings section.
  3. In the table, select a virtual infrastructure whose connection settings you want to modify, and click the Edit link above the table.

    For a virtual infrastructure based on the ALT Virtualization Server platform, KVM is displayed as the type of a virtual infrastructure that the Integration Server connects to.

    The Changing virtual infrastructure connection settings window opens.

    The Address field displays the IP address in IPv4 format or the fully qualified domain name (FQDN) of the virtual infrastructure object to which the Integration Server is connected for interaction with protected virtual infrastructure. The Address field cannot be changed.

  4. Make the necessary changes.

    You can change the following settings for connecting the Integration Server to the virtual infrastructure:

    • Protocol

      The Protocol field is displayed if you configure connection to the virtual infrastructure managed by the TIONIX Cloud Platform or to the virtual infrastructure managed by the OpenStack platform.

    • OpenStack domain

      The OpenStack domain field is displayed if you configure connection to the virtual infrastructure managed by the TIONIX Cloud Platform or to the virtual infrastructure managed by the OpenStack platform.

    • User name
    • Password
  5. If you selected a virtual infrastructure running on VMware vCenter Server in the list of virtual infrastructures to which the Integration Server connects, you can configure the use of VMware NSX Manager by Kaspersky Security. You can enable or disable the use of VMware NSX Manager, and modify the settings for connecting the Integration Server to VMware NSX Manager.

    To enable Kaspersky Security to use VMware NSX Manager, at the bottom of the Changing virtual infrastructure connection settings window, do the following:

    1. Select the Use VMware NSX Manager check box.
    2. In the VMware NSX Manager type drop-down list select one of the following items:
      • VMware NSX-V Manager, if VMware NSX Manager from the VMware NSX Data Center for vSphere package is installed on your infrastructure.
      • VMware NSX-T Manager, if VMware NSX Manager from the VMware NSX-T Data Center package is installed on your infrastructure.
    3. Specify the following connection settings:
      • New IP address in IPv4 format or the fully qualified domain name (FQDN) of the VMware NSX Manager.

        If VMware NSX-T Manager is clustered in your virtual infrastructure, specify the virtual IP address of the cluster. First assign a virtual IP address and certificate to the cluster (for more information on configuring the VMware NSX-T Manager cluster, refer to the VMware documentation).

      • Name and password of the account that the Integration Server must use to connect to VMware NSX Manager. A VMware NSX Manager account that has been assigned the Enterprise Administrator role is required.

    To change the connection settings of the Integration Server to VMware NSX Manager, at the bottom of the Changing virtual infrastructure connection settings window, specify the VMware NSX Manager type and the new account name and password.

    If you change the account password for connecting to VMware NSX-T Manager, the Integration Server can connect to VMware NSX Manager no earlier than 15 minutes after saving the new connection settings.

    To disable the use of VMware NSX Manager by Kaspersky Security, clear the Use VMware NSX Manager check box.

  6. Click the OK button in the Changing virtual infrastructure connection settings window.

    The Integration Server performs the following actions:

    1. Verifies authenticity of every virtual infrastructure object whose connection settings have been changed.

      Authenticity is not verified for a Microsoft Windows Server (Hyper-V) hypervisor.

      Authenticity verification for TIONIX Cloud Platform and OpenStack platform microservices is performed only when you use the HTTPS protocol for connecting the Integration Server to a virtual infrastructure.

      To verify authenticity, the Integration Server receives an SSL certificate or fingerprint of the public key from each virtual infrastructure object.

      If a certificate received from a virtual infrastructure object is not trusted for the Integration Server or does not match a previously installed certificate, an error message is displayed in the list of virtual infrastructure objects to which the Integration Server connects.

    2. If you enabled the use of VMware NSX Manager or changed the VMware NSX Manager connection settings, the Integration Server verifies the authenticity of VMware NSX Manager. To verify authenticity, the Integration Server receives an SSL certificate from VMware NSX Manager.

      If the certificate received from VMware NSX Manager is not trusted for the Integration Server or does not match the previously installed certificate, the Certificate verification window opens with the appropriate message. Click the link in this window to view the details of the received certificate. If you do not consider this certificate to be authentic, click the Cancel button to disconnect, and replace the certificate with a new one.

      If the certificate complies with the security policy of your organization, you can confirm the authenticity of the certificate and continue connecting to VMware NSX Manager. To do so, click the Consider certificate to be authentic button in the Certificate verification window. The received certificate will be installed as a trusted certificate on the device where the Kaspersky Security Center Administration Console is installed.

Did you find this article helpful?
What can we do better?
Thank you for your feedback! You're helping us improve.
Thank you for your feedback! You're helping us improve.