vSphere 6.5U2 support

[CPCS]

Hi,
so i opened a case at vmware and got a reply, which again leave me kind of frustrated and not knowing if or when we can expect a solution...

"VMware vSphere 6.5 U2. This update introduces preliminary support by addressing all outstanding U2-specific compatibility issues that can be managed from the Veeam side. However, there is a major regression in ESXi 6.5 U2 code that makes the vSphere API fail randomly during high host CPU load periods, consequently impacting a variety of Veeam Backup & Replication functionality. VMware is currently troubleshooting this bug, and fixing one will most likely require the new ESXi 6.5 U2 build issued."

I have no indication that the statement "there is a major regression in ESXi 6.5 U2 code that makes the vSphere API fail randomly during high host CPU load periods" is factually correct.

It would perhaps be better to say that "Veeam client connections to the vSphere API are failing for reasons that Veeam have been unable to determine, when stress testing ESXi 6.5 U2 with high load."

Reviewing the Veeam Support Forums I see that an incorrect message is being given to Veeam customers, that this is a single 'known issue' which is being actively worked on by Veeam and VMware.

vmware-vsphere-f24/vsphere-6-5u2-suppor ... 1-135.html

Specifically SR 18797316305 was referenced in this forum as "an open ticket on vmware side for this issue".
Obviously we cannot discuss the particulars of another customers case with you, but we can confirm that SR 18797316305 has been closed since December and there is no action pending on the VMware side.
The case was specific to NFC connections, and my understanding is that based on the feedback from VMware that Veeam have been checking their NFC client settings.

While we cannot rule out the possibility that Veeam have another ticket open, it's possible that there is some confusion internally at Veeam regarding the status of their investigation and that the people posting updates on the forums have not been correctly informed.

Note that there is a limit on the maximum number (25) of NFC connections in ESXi 6.5 Update 2 which does not apply to ESXi 6.7 so Veeam's note that "the issue is resolved if you move to 6.7" would indicate to me that they have confirmed this is an issue in their NFC client settings.

Our assumption is that Veeam will correct this in a future update on their side.

[wishr]

Hi CPCS,

As I mentioned in my previous post the referenced case has been closed - that particular issue has gone on the updated VDDK versions (they are part of B&R9.5 U4). We'll share more information and instructions on how to get through the given situation very soon in this thread.

Thanks

[Gostev]

Indeed, NFC issue magically went away with an updated VMware VDDK version so the original support case was closed, however the same change caused a new (2nd) reliability issue which was tracked in a separate support case.

Right now, we're in the final stage of regression testing of the latest vSphere 6.5 U2 patch level, which appear to resolve the 2nd issue. As of now, things look promising. I will update once the stability testing has been completed, and we are ready to officially support vSphere 6.5 U2 [with the latest patches installed] with our Update 4.

Note that there is a limit on the maximum number (25) of NFC connections in ESXi 6.5 Update 2 which does not apply to ESXi 6.7 so Veeam's note that "the issue is resolved if you move to 6.7" would indicate to me that they have confirmed this is an issue in their NFC client settings.

I am not exactly sure how they make the connection here... but just for the record, our NFC client has always been limited to 20 connections for vSphere 6.5. And any issue with Veeam NFC client settings would have affected all 6.5 builds, instead of being limited to 6.5 U2.

Thanks!

[Gostev]

All, we are now ready to declare official full support for vSphere 6.5 U2 patch level ESXi650-201811002 or later, with Veeam Backup & Replication 9.5 Update 4. Thank you for your patience!

[tommls]

For those of using the custom HPE ISOs because we run HPE hardware, does anyone know if the current HPE custom 6.5u2 ISO matches this level??

OR

Are we better off going from 6.5u1 to 6.7u1 instead using the relevant HPE custom ISO??

[Andreas Neufert]

You need to check with HPE...
what I can see here: https://my.vmware.com/de/web/vmware/det ... ductId=614
it is not compatible as it has old patch level. I would update anyway because of some critical patches.
Again I think it is best to discuss with HPE. Maybe my link is an old one.

[tommls]

Is this HPE build of vSphere 6.7 U1 compatible with 9.5 Update 4??

VMware-ESXi-6.7.0-Update1-10302608-HPE-Gen9plus-670.U1.10.3.5.12-Oct2018.iso

[Gostev]

Tom, you have to check with HPE support if their build includes ESXi650-201811002. But according to the date I see in the name of HPE iso, it is unlikely since ESXi650-201811002 was released in the last days of November only. Thanks!

[ghgard]

How do I find out if VMware-ESXi-6.5.0-Update2-9298722-HPE-Gen9plus-650.U2.10.3.5.5-Sep2018-depot.zip
Release Date: 2018-09-27
ESXi 6.5 U2C ESXi650-201808001 8/14/2018 9298722

is supported by 9.5 u4? This is the newest build available for my Gen8 servers, currently running 6.5 U1, but would like to get a few of the fixes installed.

Based on what I can ascertain, only 6.5 U2 versions newer than Nov-2018 are supported, is this correct?

[wishr]

Hi Grant,

Correct, we do support builds that include ESXi650-201811002 patch or later as Gostev mentioned above. The best idea is to check with HP if a certain build includes this patch.

Regards,
Fedor

[fgw]

How do I find out if VMware-ESXi-6.5.0-Update2-9298722-HPE-Gen9plus-650.U2.10.3.5.5-Sep2018-depot.zip
Release Date: 2018-09-27
ESXi 6.5 U2C ESXi650-201808001 8/14/2018 9298722

is supported by 9.5 u4? This is the newest build available for my Gen8 servers, currently running 6.5 U1, but would like to get a few of the fixes installed.

Based on what I can ascertain, only 6.5 U2 versions newer than Nov-2018 are supported, is this correct?

similar situation here with an Gen8 server!

but why not simply using this image to install 6.5U2 and apply the update ESXi650-201811002, or probably the most recent one ESXi650-201901001, right after installation?

have a look here: https://communities.vmware.com/thread/597583

u just need to take care this updates dont replace any drivers as originally installed with the HPE image. if so u may need to replace this updated drivers with supported HPE versions after applying the update. besides that i dont see an issue ...

[fgw]

btw, the image u mentioned is the Gen9 Plus Custom Image

for Gen8 u are looking for the Pre-Gen9 Custom Image:

Name: VMware-ESXi-6.5.0-Update2-9298722-HPE-preGen9-650.U2.9.6.8.3-Sep2018.iso
Release Date: 2018-09-27
Build Number: 9298722

which, regarding build number, contains ESXi650-201808001

[ghgard]

Thanks. I did realize after posting that I pasted in the wrong link.

I wish vmware would make it easier to find info on all of the version numbers. It can get very confusing.

Thanks...

[info@comnovis.de]

gostev could you please verify which is the Minimum esxi 6.5 u2 build number to run flawlessly with Veeam 9.5 u3a?
thanks alot.

[shineknox]

Correct, we do support builds that include ESXi650-201811002 patch or later as Gostev mentioned above. The best idea is to check with HP if a certain build includes this patch.

No need for them to wait for HP to provide an update image. They would be able to just apply the patch, P03; using update manager.

[wishr]

Hello everyone,

gostev could you please verify which is the Minimum esxi 6.5 u2 build number to run flawlessly with Veeam 9.5 u3a?

vSphere 6.5U2 is only fully supported by B&R9.5 Update4 and future versions due to the aforementioned VDDK issue. Please review the previous page for more information.

No need for them to wait for HP to provide an update image. They would be able to just apply the patch, P03; using update manager.

Sure, in case if patch installation fits your use-case you can stick with this scenario.

Regards,
Fedor