topic Re: Two Node New Deployment 3.7.10 in HPE SimpliVity

Two Node New Deployment 3.7.10

sampiyonts — Tue, 17 Dec 2019 07:21:59 GMT

Hello,

When we are trying new system, everytime receive "Simplivity Battery Backup Health Error" and when enable HA after installing "Insufficient Vsphere HA failover resources"

Re: Two Node New Deployment 3.7.10

DaveOb — Tue, 17 Dec 2019 10:22:56 GMT

Battery backup health error will need a support case.

The Insufficient Vsphere HA failover" alarm is due to admission control in Vmware HA more details can be found in https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-a00088847en_us&docLocale=en_US page 38

Re: Two Node New Deployment 3.7.10

sampiyonts — Tue, 17 Dec 2019 13:01:04 GMT

Hello

Battery backup health error will need a support case.--- There is no hardware or Fw issue,

Admission control is choose 1 host ,

Re: Two Node New Deployment 3.7.10

DaveOb — Tue, 17 Dec 2019 14:25:37 GMT

Did you calculate the memory reservation as per the document ?

Due to the way VMware takes into account the OVC as a VM,it accounts for it in HA even though the OVC can never be failed over and reports a violation ,In a two node cluster you may as well disable admission control.In the event of a VMware HA failover ALL VMs will be restarted on the remaining node.

Regards the battery error a review of the AHS logs would be needed.

Re: Two Node New Deployment 3.7.10

sampiyonts — Tue, 17 Dec 2019 15:27:59 GMT

i didnt find memory reservation as per the document

Re: Two Node New Deployment 3.7.10

OzgurT — Tue, 17 Dec 2019 17:28:16 GMT

Battery Backup healt error iis false error and will be fixed next release of software..For the HA part you need to set up admission control coreectly.If you disable the addmision control then the error will gone.

Re: Two Node New Deployment 3.7.10

sampiyonts — Wed, 18 Dec 2019 06:42:10 GMT

Thx,

Re: Two Node New Deployment 3.7.10

cheesi — Wed, 18 Dec 2019 06:54:16 GMT

You are correcct. Batterie has no errors in the ILO. Reset is onte time error will be gone. Is always after a redeployment.