VMTN

I checked this morning and there are a few options. 1) Apply a debug build of ESXi that will still be affected by the problem but gather more information for the development team, 2) There is a script that has to be run at each boot of each ESXi server that they believe fixes the issue entirely but can cause performance degradation, 3) Downgrade to 5.5 or below.

My case has now been open 60 days regarding this issue. It's very disappointing.

hello,

i have the same problem with 2 hp dl 580 G7.

any chance you could share the script to run on each reboot ?

thanks !

The fix script for this is now available here.

That KB article seems to have been published today, the same day 6.0 U1 came out.  No mention that 6.0U1 fixes this problem.  In fact it specifically states "After upgrading to or installing ESXi 6.0.x and ESXi 6.0 Update 1, you may experience these symptoms" so one would have to assume the problem still persists in 6.0 U1 also.  If it was fixed in 6.0 U1, I would expect the article to say as much.

Hi,

Check below article, It could be firewall issue at VC, hope this will help

VMware KB: ESXi/ESX hosts enter a Not Responding state after connecting to vCenter Server

Thanks for the info. I guess I will wait for the patch I don`t want to run into performance issues:(

VMware really needs to have a warning on their download page that references this KB.

Did you try to connect ESXi using VI Client directly?is it working?

1) I would suggest to try starting managment agent and see if it works.

2) The very moment you try connecting ESXi to vCenter sevrer , have vCenter Server logs been open to analyse the logs and identify the cause of problem.

In my case you couldn`t try it even when accessing it through the console. The host appears to be locked up.

I have not seen this issue before and I have been working with Vmware since version 3.

Neither i had came across such problem.

In ESXi, there are several menu options provided to test the management network. If the ESX host responds to user interaction, but does not respond to pings, you may have a networking issue.

As stated by you that you are not even able to access the console. Can you check what the Enclosure says about the state of host? What i suspect is the hardware might be incompatible with version 6 or vice versa.

try rollback the settings and check if the blade respond well. If yes, then suggest you to first update hardware firmware/bios version and then install ESXi 6.x

Neither i had came across such problem.

In ESXi, there are several menu options provided to test the management network. If the ESX host responds to user interaction, but does not respond to pings, you may have a networking issue.

As stated by you that you are not even able to access the console. Can you check what the Enclosure says about the state of host? What i suspect is the hardware might be incompatible with version 6 or vice versa.

try rollback the settings and check if the blade respond well. If yes, then suggest you to first update hardware firmware/bios version and then install ESXi 6.x

Hi ,

Check below KB,

VMware KB: Troubleshooting an unresponsive host and multiple Disconnected virtual machines

ESXi 6.0 network connectivity is lost with NETDEV WATCHDOG timeouts in the vmkernel.log (2124669)

check the KB

VMware KB: Troubleshooting an unresponsive host and multiple Disconnected virtual machines