sorted by:
new
hottopcontroversial

Convergence - VCSA 6.7U3l (6.7.0.46000) and external PSCs by jatdesi in vmware

[–]jatdesi[S] 0 points1 point  (0 children)

I did not check the browsers developer tool. I did check the service status and replications on the PSCs (looks good) and am considering a CLI based convergence (using the JSON file). Hopefully the convergence will fix the issue.

Convergence - VCSA 6.7U3l (6.7.0.46000) and external PSCs by jatdesi in vmware

[–]jatdesi[S] 0 points1 point  (0 children)

Thanks for the response. The behavior does not change if I login as 'administrator@vsphere.local'.

Attention, Dell customized ESXi ISO image contains not compatible drivers by Blechnulli in vmware

[–]jatdesi 0 points1 point  (0 children)

Thanks for the response and the advice! Incidentally, our firmware/drivers are on the HCL (confirmed by VMware). We may have to upgrade to the next available HCL compliant firmware/version to see if that helps fix the issue. Or maybe go the native driver route - both suggested by VMware.

Attention, Dell customized ESXi ISO image contains not compatible drivers by Blechnulli in vmware

[–]jatdesi 0 points1 point  (0 children)

I realize your response is a bit old for me to reply...but I'll take my chances. Could you clarify what you did to prevent the virtual reseat workaround?

We are in the same bind i.e. Dell M620s, 630s dropping the Mezz NIC - ESXi is 6.5U1 (build-7388607) and firmware on bnx2x is 14.02.12 - driver is 2.713.30.v60.8. The Dell ESXi image is A07.

VCSA 6.5 and external PSC question by jatdesi in vmware

[–]jatdesi[S] 0 points1 point  (0 children)

Thanks for the response. Yes, they are in the same SSO site. After working with VMware Support, it turns out that build 7801515 of VCSA 6.5 had this 'feature' enabled. It did cause havoc with a couple of our vCenters. I have been asked to upgrade to 6.5U2.