VMware Cloud Community
sc_lodestar
Contributor
Contributor
Jump to solution

Deploy VCSA 7.0.3 U3J stuck in stage 1 initializing

Hi all

 

I download the VMware-VCSA-all-7.0.3-20990077.iso and want to deploy in my new Exsi,but I faild at stage 1,no response...

I check the log:

2023-01-29T09:52:41.582Z - debug: checking if 130.*.1.54 exists in the network of vimConn: undefined
2023-01-29T09:52:41.582Z - debug: isIp: 130.*.1.54: true
2023-01-29T09:52:41.582Z - debug: getVmWithIPFQDN: hostName 130.*.1.54 is associated with [ '130.*.1.54' ]
2023-01-29T09:52:41.661Z - debug: token:undefined, length:7, running total:7
2023-01-29T09:52:41.661Z - error: No VM found with hostname 130.*.1.54
2023-01-29T09:52:41.706Z - debug: Error in getVmWithIPFQDN: No VM found with hostname 130.*.1.54
2023-01-29T09:52:41.707Z - info: Network Prechecks Succeeded

My DNS works well :

C:\Users\Administrator>nslookup
server: UnKnown
Address: 130.*.1.67

Non-authoritative answer:

name: vcsa.*.com
Address: 130.*.1.54

If I use Cli to install and  I get the log :

[START] Start executing Task: Invoke OVF Tool to deploy VCSA for installation,
upgrade, and migration at 10:20:55
Failed to collect support bundle from the deployed appliance 'vCenter server'.
Exception: Cannot collect the support bundle because Cannot find the appliance
'vCenter server' on the ESXi host '130.*.1.33'. Exception: Failed to find VM
vCenter server
================ [FAILED] Task: Precheck ovftool commandline parameters to
deploy a vCenter Server Appliance execution failed at 10:20:56 ================
================================================================================
Error message: ApplianceDeploymentTask: Caught an exception
(vim.fault.RestrictedVersion) { dynamicType = <unset>, dynamicProperty =
(vmodl.DynamicProperty) [], msg = 'Current license or ESXi version prohibits
execution of the requested operation.', faultCause = <unset>, faultMessage
= (vmodl.LocalizableMessage) [] }
=================================== 10:20:56 ===================================

 

So does it missing support bundle? How to solve?

Reply
0 Kudos
1 Solution

Accepted Solutions
sc_lodestar
Contributor
Contributor
Jump to solution

I have solved this problem

reason is using the free license 

but there is no log told me my license do not work

View solution in original post

6 Replies
a_p_
Leadership
Leadership
Jump to solution

The logs suggest that you are trying to deploy the vCSA using its IP address as the host name, but you also mention DNS.
Please clarify how you are trying to deploy the vCSA. Note that in case of using the FQDN, you need forward (Host-A), and reverse (PTR) DNS resolution.

Some other thoughts:

  • Since you are trying to install a vCSA, can I safely assume that the ESXi host is not already managed by vCenter Server? If it is, and DRS is active, the newly deployed appliance may have been powered on on a different host.
  • Are any firewall rules active between the system from which you deploy the vCSA, and the ESXi host?
  • Does the physical switch to which the ESXi host is connected allow multiple MAC addresses on a single port?

What you may try to troubleshoot this issue, is to install e.g. a small Linux VM on the host, and assign it the vCSA's designated IP address to see whether it is accessible.

André

Reply
0 Kudos
sc_lodestar
Contributor
Contributor
Jump to solution

No, I use 'vCenter server' as the host name

I have tried the following step:

1. null DNS ip and null FQDN 

2.DNS ip ==  host ip

3.FQDN and DNS are correct

4.Gui and Cli setup follow  the tutorial in youtube or the other websites/forums/blogs

Unlucky I failed in the first step and I found No answers in Google.

 

Reply
0 Kudos
a_p_
Leadership
Leadership
Jump to solution

Mabe there's a misunderstanding.

'vCenter Server' is likely the VM's display name.
The "Hostname" that you enter in the deployment wizard's settings is likely 'vcsa.*.com'

According to your first post the name resolution for this name returns the IP address.
What about the revers DNS lookup

nslookup 130.*.1.54

Does it resolve to the hostname 'vcsa.*.com'?

André

Reply
0 Kudos
sc_lodestar
Contributor
Contributor
Jump to solution

Yes

F:\vcsa-cli-installer\win32>nslookup vcsa.*.com
Server: UnKnown
Address: 130.*.1.67

Server: vcsa.*.com
Address: 130.*.1.54


F:\vcsa-cli-installer\win32>nslookup 130.*.1.54
Server: UnKnown
Address: 130.*.1.67

Server: vcsa.*.com
Address: 130.*.1.54

Reply
0 Kudos
sc_lodestar
Contributor
Contributor
Jump to solution

I have solved this problem

reason is using the free license 

but there is no log told me my license do not work

nikhilborlesg
Contributor
Contributor
Jump to solution

Hi All, I faced this issue while installing VCenter 7.

I read here [https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCENTER-8-0-installer-hangs-on-quot-ini... that If your ESXi is running the Free license, VCenter server setup gets stuck at "Initializing" during Stage 1.

I removed the Free license from my ESXi and tried again, the VCenter server setup progressed like a breeze.

 

Hope this helps someone.

Reply
0 Kudos