vRealize appliance connectivity issue with my server Iaas

[Mohamed_cloud]

Hello everyone,

I'm a junior cloud architect and I'm deploying vRealize Automation for a Proof of Concept. I already deploy the appliance on my vCenter but during the configuration with the wizzard from Prerequisite checker step, it shows: .

And when i click run button for check the prerequisites in the Iaas server, it never show the list of prerequisites for the Iaas server.

It stucks on "Waiting for host to trigger prerequisite check".

If i can't know if my Iaas server meet all the requirements, i can't take the risk to pursue the installation, it will fail.

Thank's for the interrest.

[daphnissov]

• If you don't have enough room for a separate SQL VM, you're probably wasting your time. This is a required piece of infrastructure to support any sized vRA installation.
• If you have not deployed the vRA appliance with all correct information (including a hostname that is FQDN), I recommend you re-deploy at this point. It's not like you're trashing anything that was working.
• Please go through the installation documentation on the vRA website. All of these things are very specifically called out. https://docs.vmware.com/en/vRealize-Automation/7.3/vrealize-automation-73-installation-and-configura...

[Mohamed_cloud]

I'm deploying the appliance with this time, the correct configuration: FQDN instead of short names, domain search path.

I am waiting the sys admin to ask her about the DNS record.

[Mohamed_cloud]

I set the right FQDN and set domain search path.

Maybe it's not so important but on the next step i don't see Power on after deployment.

[Mohamed_cloud]

Hello daphnissov​,

I finished the deployment but this is what i see in the appliance console. So i have to configure the network manually. It's not normal. When the appliance console starts, it ask me to enter the new Password. It seems my configurations was not saved.

I finally configure the network manually in the appliance console: .

I installed Windows server 2012 OS for my Iaas server not server 2012R2 but server2012

[daphnissov · Accepted solution]

Deploy it again through vCenter as something went wrong. You should be using vRA 7.3 and not the older 7.2 release.

[Mohamed_cloud]

I finally deployed vRealize Automation v7.3

I set the right FQDN and domain search path and you can see below a screenshot of the appliance console:

Now i can configure the Iaas server.

[Mohamed_cloud]

Hi daphnissov​,

, Thanks Thanks, Thanks... now the prerequisite checker show me the prerequisite that are not met. I think the issue come from my previous OVA file(VMware-vR-Appliance-7.2.0.381-4660246_OVF10).

I deployed the new one (VMware-vR-Appliance-7.3.0.536-5610496_OVF10) and for now I'm good.

Now it's time to resolve the prerequisites in my Iaas. Let's begin the job.

[sarikrizvi]

Issue :- Network connectivity issue in between vRA and IaaS server

Troubleshooting Steps #

1.  Redeploy vRA appliance through OVA from vCenter and it will pick IP, dns, other config automatically.
2.  Test Ping vRA = IaaS server and Run nslookup host-name
3.  Use service account for installation of management agent which have "local administrator" access on windows server .

4. "Time Offset" should show 0 in config wizard and if it's showing something bigger number then it would be problem .

Use above three steps and issue will get resolved

[sarikrizvi]

Issue :- Network connectivity issue in between vRA and IaaS server

Troubleshooting Steps #

1.  Redeploy vRA appliance through OVA from vCenter and it will pick IP, dns, other config automatically.
2.  Test Ping vRA = IaaS server and Run nslookup host-name
3.  Use service account for installation of management agent which have "local administrator" access on windows server .

4. "Time Offset" should show 0 in config wizard and if it's showing something bigger number then it would be problem .

Use above three steps and issue will get resolved

[daphnissov]

These are extremely generic steps (did you even read this thread?) and are not guaranteed to resolve anything. There are far more troubleshooting steps to be performed with more complexity than just four things.

[sarikrizvi]

I applied those steps and issue get resolved at my end, just give an try and let's see