StoreVirtual Storage
1745871 Members
4207 Online
108723 Solutions
New Discussion юеВ

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

 
danevald
Advisor

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

After having a PSOD following the install of the MEM module I found this post. Here's my setup and workaround/fix to "quickly" move on:

HP DL380G9 running ESXi 6.0u2 fully patched feb2016, running Storevirtual VSA 12.5

If you get the PSOD, just disable the switchports where iSCSI is connected and boot the server, then it boots up, uninstall the module and reconfigure the Path policy on each iSCSI path to use either MRU or Fixed, then boot the server, enable ports again while booting, install module again, boot server, change path policy to HP LH policy, boot again.

This seems to work for me - using the 12.6 MEM module, but seeing quite a lot of "path errors" on the Alt+F12 log, and seeing CHAR_Driver ALL DONE in Alt+F11, I hope this will stop eventually...maybe after upgrading VSA to 12.6.

Stor_Mort
HPE Pro

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

There will be a new version 12.6.0.20 of the MEM driver available this month (Feb 2017) which fixes all known bugs. It will be compatible with LHOS 12.5, 12.6 and 12.7.

If the path errors don't go away after updating, check this VMware article. ATS heartbeat failure sometimes produces path failure messages. 

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113956

 

I am an HPE employee - HPE SImpliVity Support

Accept or Kudo

Johannes_we
Frequent Advisor

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

So I┬┤m running 12.6.0.20 on ESXI 6.0 U2 Build 4600944 but still see lot┬┤s of char_driver: ALL Done.

Shouldn┬┤t this have been fixed in 12.6.0.20?

Johannes_we
Frequent Advisor

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

right in that second i got a PSOD so i think i┬┤ll go back to RoundRobin native VMware.

vsamem.PNG

BenLoveday
Valued Contributor

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

Anyone else seeing issues with the new MEM driver?

We are running the older 12.6.0.14 with vSphere 6.0U2 and are seeing a lot of random performance issues. Some clusters are rock solid, others have latency going through the roof.

If we switch to the RR PSP we sometimes hit a PSOD which is not great.

Does anyone have any release notes specific to the MEM driver only? The 12.7 LHOS release notes are very generic and don't mention anything in particular to the MEM which is frustrating.

Cheers,

Ben

SVprodmgr
Frequent Advisor

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

Hi Ben, there is a customer advisory on the PSOD: http://h20566.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=4118659&docLocale=en_US&docId=emr_na-c05393399 on that version of 12.6.

Also, we have a separate multipathing user guide that might be helpful with MEM questions: http://h20566.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=4118659&docLocale=en_US&docId=emr_na-c05049830

Amy Mitchell

StoreVirtual Product Manager

I'm an HPE employee working in product management
BenLoveday
Valued Contributor

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

Thanks Amy!

I actually missed the multipathing guide recommendation on the delayed ACK. We worked with HPE support a few years back and at that time they didn't have a firm answer on disabling this so good to know it's the recommendation.

I'd really like to see a separate set of release notes for the MEM as I've seen several versions of the MEM released completely separate to the LHOS with no detail on what the updates have fixed.

Appreciate your help :-)

Cheers,

Ben

ComboIT
Occasional Visitor

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

Spoiler
 

We're on MEM 12.6.0.20 and we're seeing repeated 'WARNINGS' like this hit the vmkernel log every five minutes:

2017-07-27T03:13:31.248Z cpu13:962933)WARNING: HPE_SATP_LH: satp_lhn_updatePath:430: In satp_lhn_updatePath setting path state to OK. vmhba32:C2:T1:L0
2017-07-27T03:13:31.248Z cpu6:964156)WARNING: HPE_SATP_LH: satp_lhn_updatePath:430: In satp_lhn_updatePath setting path state to OK. vmhba32:C2:T3:L0
2017-07-27T03:13:31.248Z cpu0:964778)WARNING: HPE_SATP_LH: satp_lhn_updatePath:430: In satp_lhn_updatePath setting path state to OK. vmhba32:C2:T0:L0
2017-07-27T03:13:31.249Z cpu8:960178)WARNING: HPE_SATP_LH: satp_lhn_updatePath:430: In satp_lhn_updatePath setting path state to OK. vmhba32:C2:T2:L0
2017-07-27T03:13:31.249Z cpu13:962933)WARNING: HPE_SATP_LH: satp_lhn_updatePath:430: In satp_lhn_updatePath setting path state to OK. vmhba32:C3:T1:L0

(this is a small sample, it's actually 32 events logged every 5 minutes).

I've tried disabling ATS heartbeat but this has made no difference. Does anyone have any ideas?

Thanks

David

vdepagter
Occasional Visitor

Re: Problem installing HPE StoreVirtual Multipathing Extension Module for Vmware vSphere

I had a host yesterday that was unresponsive for management. Unable to connect with vSphere Client or through the Web Client. This started happening after attempting to spin up a Veeam SureBackup/Virtual Lab. A process in which (I guess) it connects different storage. The host showed disconnected in vCenter Server, the console was responding very delayed (by minutes). Alt+F12 showed floods of HPE_SATP_LH messages (see below). VM's were running fine. It eventually recovered. I rebooted it and rediscovered the iSCSI Static Paths as a precaution afterwards.

ESXi 5.5.0 build 4345813 (5.5U3+), hpe-lh-mem 5.5.0-12.6.0.20 connecting to 8x StoreVirtual 4530 12.6.0.155.

/var/log # tail vmkernel.log | grep -i "satp_lhn_pathfailure" | more
2017-07-30T17:34:24.396Z cpu10:61485)WARNING: HPE_SATP_LH: satp_lhn_pathFailure:1194: In satp_lhn_pathFailure unknown failure.
2017-07-30T17:34:24.449Z cpu46:65747)WARNING: HPE_SATP_LH: satp_lhn_pathFailure:1047: In satp_lhn_pathFailure status = 9 sense key = 4 and sense code = 2. path vmhba33:C0:T2:L0
2017-07-30T17:34:24.449Z cpu46:65747)WARNING: HPE_SATP_LH: satp_lhn_pathFailure:1048: path=vmhba33:C0:T2:L0 cmd[0]=c1 cmdid=8527
2017-07-30T17:34:24.449Z cpu46:65747)WARNING: HPE_SATP_LH: satp_lhn_pathFailure:1194: In satp_lhn_pathFailure unknown failure.
2017-07-30T17:34:24.502Z cpu16:66083)WARNING: HPE_SATP_LH: satp_lhn_pathFailure:1047: In satp_lhn_pathFailure status = 9 sense key = 4 and sense code = 2. path vmhba33:C1:T2:L0
2017-07-30T17:34:24.502Z cpu16:66083)WARNING: HPE_SATP_LH: satp_lhn_pathFailure:1048: path=vmhba33:C1:T2:L0 cmd[0]=c1 cmdid=8529
2017-07-30T17:34:24.502Z cpu16:66083)WARNING: HPE_SATP_LH: satp_lhn_pathFailure:1194: In satp_lhn_pathFailure unknown failure.

Additionally, I'm seeing the same WARNINGS David is having displayed on all hosts using the below combinations of software. Also seeing the "char_driver:  ALL DONE" message on the console Alt+F11 screen. These messages may have occurred during the time of the system boot.

VMware 5.5.0 build 4345813, hpe-lh-mem 5.5.0-12.6.0.20 connecting to 8x StoreVirtual 4530 12.6.0.155.

VMware 5.5.0 build 4722766, hpe-lh-mem 5.5.0-12.6.0.14 connecting to 8x StoreVirtual 4530 12.6.0.155.

I have not disabled VTS heartbeats. I have also not disabled Delayed ACK, as I found we are supposed to according to the MEM installation guide. http://h20566.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=4118659&docLocale=en_US&docId=emr_na-c05049830