topic 3 Node VSA - Gen 10 ESX Host patching question in StoreVirtual Storage

3 Node VSA - Gen 10 ESX Host patching question

regi_p — Thu, 11 Jan 2018 15:23:15 GMT

I have the above & like to patch the Gen 10 host to System ROM Version 1.28 from 1.20 on my Gen 10 ESX host

https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00039267en_us

And patch VMW 6.5 as well. Is this below steps correct ?

1) VMotion all VM's to ahother host & Shutdown VSA from CMC

2) Update BIOS reboot >> Patch VMW 6.5 >> After reboot power on VSA

3) After some time thei VSA will show in CMC

4) LUNS's will resync & You can do ths same for the remaining ESX hosts

Before shutting down VSA from CMC do I have to stop any running manager(s) ? I'm on latest 12.7 OS

Please advise

Re: 3 Node VSA - Gen 10 ESX Host patching question

Bart_Heungens — Thu, 11 Jan 2018 15:48:41 GMT

Hi,

The easiest is to put the ESXi host in maintenance mode. Normally all VM's will be moved to other ESXi hosts in the cluster (depending of HA and DRS settings). Only the VSA needs to be shut down manually... No need to stop the manager manually.

At that moment patch the firmware and OS and reboot the ESXi host... Start the VSA manually (even better put it in autostart mode as first VM) and let it sync the changes from the other VSA's in the cluster.

Once the VSA cluster is normal, repeat this procedure on the other hosts...

FYI on my blog I have an article about how I obtained 7 years of 100% uptime (should update the article is 8 years meanwhile) with my VSA cluster

http://www.bitcon.be/100-uptime-for-7-years-with-storevirtual-vsa-check/

Kr,

Bart

Re: 3 Node VSA - Gen 10 ESX Host patching question

regi_p — Thu, 11 Jan 2018 19:08:59 GMT

Thanks Bart point taken

I stopped the running manager by accident before shutting dowin the VSA and when it came back it said the below

Phoned support & they sorted it

Re: 3 Node VSA - Gen 10 ESX Host patching question

Bart_Heungens — Thu, 11 Jan 2018 19:17:53 GMT

Hi,

This is indeed possible allthough I never saw this error in real life before... Just do a clean shutdown of the VSA and you should be OK...

Good that everything is (re)solved...

Kr,

Bart