Hello,
I’ve a simple cluster HA witch 2 host (Fujitsu RX2540M2 and HP DL380p Gen8).
I’ve installed on them Custom ESXi 6.5 update 1 ISO (Fujitsu and HP).
Fujitsu – 6.5.0-5969303
HP – 6.5.0-6765664
The 2 hosts are connected directly via iSCSI (1GB) to Fujitsu Eternus DX60S2.
Both of the hosts have instead one Network Card dual port 10GB X540-AT2 (not used in any vSwitch for the moment).
I’ve configured update Manager for this cluster and after Scan for Update I’ve my 2 hosts non compliant.
I’ve tryed to Stage Patch on HP (first of all) but I’ve got the following error:
cannot download software packages from patch source. check the events in the update manager log for download details
Can somebody help me in this problem?
Thanks and regards
Luca
The last updates have been pulled from the update location, but the metadata in the Update Manager might still be there. To resolve this, create a fixed patch baseline, and make sure you exclude the January patches.
André
Hello André,
I've followed your indication and the Update process has started, now is upgrading, I'll let you know if everything will finish correctly.
But can you explain me what's happened exactly? And for next update can I create and attach again the dynamic patch baseline?
Thanks again
Luca
Due to Intel's CPU microcode issues, VMware pulled down the January patches from the online and offline portal (see https://kb.vmware.com/s/article/52345).
I guess that the patches will become available again shortly (with a fixed microcode), which should allow to use dynamic baselines again.
André
Hello André,
I've followed the step and the Update Manager has worked, but I've got a PSOD (attached photo) after host reboot.
After the first part I've reached the server via ping again (in the reboot procedure), but I've few minutes the ping has stopped again.
In the host there's installed an Intel Dual Port 10GB X540-AT2 (even if at the moment isn't used, but I'll need next month).
Any idea?
Regards
Luca
Please take a look at http://www.provirtualzone.com/psod-after-apply-esxi-6-5-update-1-hpe/ which describes such an issue, and how to resolve it.
André
PS: I just found a HPE Advisory regarding this issue: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00030080en_us
Hi André,
I've found that link and I'll make some test.
I think that is the problem
Regards
Luca