Sky Health Diagnostic v4 stuck at first start

[massimo]

Hi All, and sorry for my English,

vCenter 8.0.1
Esxi hosts 6.7 in vSAN cluster

We are trying with no luck to install VMware-Skyline-HealthDiagnostics-Appliance-4.0.0-21961090_OVF10 via vCenter Wizard.

Everything go fine until the new created VM power on.

As for attached screenshot, new created VM start and stuck after "Started Appliance initialization script" and, in the mean time, in the vCenter we have "Install Solution" task at 0%.

After about 2 or 3 hours, VM is in the same condition and task fail for timeout.

Nothing change if we try to deploy directly the OVA by normal vCenter way and so without use the specific Sky Health wizard.

Nothing change also rebooting the VM. It arrive in the login prompt but the web interface is unreachable.

Can someone help me to find our mistake?

Thanks in advance for any help.

Best regards.

Massimo

[araikwar · Accepted solution]

Hi Massimo,

The firstboot script is not stuck. After powering on the VM just wait for 5 min and you can access it.

For accessing VM console, press Enter and provide authentication credentials.

Let me know if you can access SHD.

Thanks

Ashish

[massimo]

Hi Ashish,

with your suggestion I finally managed to start the application. Thank you.

Just to understand and update our internal information, please can you help me to understand:

1. Where is documented step that you suggested

2. What is the meaning of creating a special wizard for delivery, which starts from the Virtual center and asks which is the destination Virtual center but which waits (until failing) for a step without providing any indication on how to proceed?

Thanks again.

Best.

Massimo

[araikwar]

Hi Massimo,

Please check step 11 of Section "Deploy VMware Skyline Health Diagnostics Using the OVA Image" of "VMware Skyline Health Diagnostics Install and Configure Guide".  Direct link is at Deploy VMware Skyline Health Diagnostics Using the OVA Image 

Thanks

Ashish

[araikwar]

Hi Massimo,

I hope the issue is resolved.

Could you please update thread with fix details and mark it as resolved?

Thanks

Ashish

[massimo]

Hi Ashish,

and first of all, apologize for my delay in reply.

After your suggestion, that i just marked as right, we was finally able to run the appliance.

In my personal opinion, documentation is low clear about the point that stuck us but, anyway, after having left the application to work for a few weeks, we removed it because, in our opinion, it was too confusing in the way of providing information.

It is clearly not my intention to "criticism" the application but that is not what we were looking for.

Thanks and sorry again for delay.

Best regards.

Massimo