[OmniOS-discuss] stmfproxy ALUA RSF-1

[Machine Man]

Sorry Dan I just realized that I hit replay and not replay to the mailing list.


I opened a support case with High Availability, they verified the cluster configuration and all checked out good. I was also told that the messages in my 1st message are to be expected.
They mentioned that they have been seeing issues with VMware 5.5U3 and up and its a VMware ALUA issue. I am not really finding anything out there as far as complaints around it being a VMware issue and was wondering if anyone else is using RSF-1 with VMware. (They are doing a force-lip on a workaround, but this is not doing anything in our case.)

With ALUA enabled its slow and when failing over connection to the LUN never returns. Disabling ALUA it works well, but a rescan is needed in VMware after the failover leaving us in the cold for unexpected failures when a failover is done triggered. This is a plus for scheduled maintenance Im just not sure for the price if its worth it.

We don't run critical systems on the OmniOS storage targets, but they are connected to VMware clusters that run business critical systems. Anyone that have dealt with an APD event in VMware would understand my concern here.

I would like to just mentioned that I just completed testing with windows and I have the exact same results, in fact it worse and it results in a hard boot for the windows machine.

Any feedback from anyone using RSF-1 with OmiOS will be appreciated.


________________________________
From: Dan McDonald <danmcd at omniti.com>
Sent: Monday, March 6, 2017 9:34:11 AM
To: Machine Man
Cc: omnios-discuss at lists.omniti.com; Dan McDonald
Subject: Re: [OmniOS-discuss] stmfproxy ALUA RSF-1


> On Mar 5, 2017, at 12:56 PM, Machine Man <gearboxes at outlook.com> wrote:
>
> I see the following on both nodes:
>
>  [ID 602194 daemon.warning] recv() call failed: 0
>  [ID 682322 daemon.warning] postMsg() no transport handle
>
> I am assuming this is related to my problem?

This is likely an RSF-1 problem. Have you checked with them about this yet?

Dan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20170314/761345ec/attachment.html>