VMware Networking Community
commando30
Contributor
Contributor
Jump to solution

NSX upgrade from 6.2.5 to 6.3.3 fails at Host Preparation - Installation Status = Not Ready

Hi,

We need support with an NSX upgrade from 6.2.5 to 6.3.3

We've followed the procedure and most of it worked, except for the Host preparation status:

- The NSX Manager was upgraded successfully.

- The Controller cluster was upgraded successfully.

- The upgrade of the vibs appears to have failed because the "Installation Status" of all the Hosts and of the Cluster says "Not Ready". The "Firewall" and "VXLAN" columns say "Enabled" and "Configured", respectively, both with a green checkmark.

- The DLRs and ESGs were upgraded successfully.

Clicking on "Resolve" under "Actions" of each Host or the Cluster itslef does not change the status.

We've tried to find info about this, but nothing that points us in the right direction. How can we fix it?

Thank you.

Alfonso

0 Kudos
1 Solution

Accepted Solutions
commando30
Contributor
Contributor
Jump to solution

Never mind, I fixed it restarting the EAM (ESX Agent Manager) in vCenter and that fixed it almost instantly.

I went to:

Administration - System Configuration - Services - VMware ESX Agent Manager

Right-click - Stop

Right-click - Start

Wait until:

Health:     Good

State:     Running

I now really don't know how I came across that, but I read it at somebody's post, I gave it a try and it solved my problem.

Thanks.

Alfonso

View solution in original post

0 Kudos
4 Replies
Sreec
VMware Employee
VMware Employee
Jump to solution

Can you please provide me with output of /var/log/esxupdate.log from one of the host ?

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 7x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
0 Kudos
amolnjadhav
Enthusiast
Enthusiast
Jump to solution

Hi,

Can you please provide me the output of following commands from one of the ESX host?

   #cat /etc/vmware/netcpa/config-by-vsm.xml

   #service netcpad status

Please consider marking this answer "correct" or "helpful" if you think your query have been answered correctly. Regards Amol Jadhav VCP NSXT | VCP NSXV | VCIX6-NV | VCAP-DCA | CCNA | CCNP - BSCI
0 Kudos
commando30
Contributor
Contributor
Jump to solution

Never mind, I fixed it restarting the EAM (ESX Agent Manager) in vCenter and that fixed it almost instantly.

I went to:

Administration - System Configuration - Services - VMware ESX Agent Manager

Right-click - Stop

Right-click - Start

Wait until:

Health:     Good

State:     Running

I now really don't know how I came across that, but I read it at somebody's post, I gave it a try and it solved my problem.

Thanks.

Alfonso

0 Kudos
amolnjadhav
Enthusiast
Enthusiast
Jump to solution

Thanks for sharing

Please consider marking this answer "correct" or "helpful" if you think your query have been answered correctly. Regards Amol Jadhav VCP NSXT | VCP NSXV | VCIX6-NV | VCAP-DCA | CCNA | CCNP - BSCI
0 Kudos