Problem

Error Failed to get IP addresses for connecting to SVM appears during SVM deployment.

Solution

To troubleshoot this problem, you need to follow our step-by-step guide:

I. Disable SVM rollback

• Go to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIIS Console\ for KSV LA 5.1 or to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIISLA Console for KSV LA 5.2
• Edit the Kaspersky.VIISConsole.UI.exe.config file
• Uncomment <!--<add key="disableRollback" value="1" />--> (delete <!-- and-->)
• Save changes

II. Enable VIIS traces

• Go to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIIS\ for KSV LA 5.1 or to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIISLA for KSV LA 5.2
• Open NLog.config file in a text editor
• Find the line <logger name="*" minlevel="Info" writeTo="file"/> and change minlevel value from Info to Trace
• Save changes

III. Enable extended logging of deployment wizard

• Go to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIIS Console\ for KSV LA 5.1 or to C:\Program Files (x86)\Kaspersky Lab\Kaspersky VIISLA Console for KSV LA 5.2
• Open NLog.config file in a text editor 
• Find the line <logger name="Kaspersky.Virtualization*" minlevel="Info" writeTo="DeployWizardLog" final="true"/> and change minlevel value from Info to Trace for KSV LA 5.1 and <logger name="DeployWizardFileLogger" minlevel="trace" writeTo="DeployWizardLog" final="true"/> and change minlevel value from off to Trace for KSV LA 5.2
• Save changes

IV. Start troubleshooting

1. Start SVM deploying wizard and don’t forget to enable option Allow remote access via SSH for root account.
2. Wait for the error and then, make sure that deployment wizard skipped rollback step.
3. Disable all traces returning to the previous values.
4. Connect to SVM directly, using hypervisor.

5. Login to SVM OS under the root account, using default password 7czWtTKhCgrvEYBHb3rE

   This password can be applied only during troubleshooting process with disabling SVM rollback and it wouldn't work with normally deployed SVMs.
6. Use command ifconfig to check if the SVM received network adapter settings, specified at the beginning of installation.
7. Try to establish connection by SSH from KSC (where VIIS installed) to the SVM. If SSH connection fails, then there are no issues with Kaspersky product. You should configure the environment according to our system requirements. Especially, at the side of ports accessibility. Configuring ports used by the application

8. If the SSH connection established successfully, please collect the following data and send it to Kaspersky Support: 

   Data to be collected

   • Screenshot of network settings that has been applied to the SVM
   • VIIS log from - C:\ProgramData\Kaspersky Lab\VIIS\logs for LA 5.1 and C:\ProgramData\Kaspersky Lab\VIISLA\logs\ for LA 5.2
   • Deployment wizard detailed log from - C:\Users\<Account>\AppData\Local\Kaspersky_Lab\ViisConsole for LA 5.1 and  C:\Users\<Account>\AppData\Local\Kaspersky Lab\Kaspersky VIISLA Console\logs\ for LA 5.2
   • /var/log/ – from SVM
   • /var/opt/– from SVM