On 10/02/2018 10:10 AM, Bernhard Dick wrote:
Hi,
Am 02.10.2018 um 16:59 schrieb Christopher Cox:
> You usually have to specify that the LUN has to be accessible to
> multiple systems (e.g. like a clustered filesystem would). It's not
> unusual for a system to default to allowing only one initiator to
> connect.
the problem is not that not multiple initiators are unable to connect
(that runs well), but that I see the LUNs only on one of the two
controller ports, as the storage decided that the Top Controller is
currently the active one. I can login to the second controller, but that
does not present any LUNs to any of my servers.
Maybe I should have written active controller instead of active system.
In an active active case the exposed LUN will show all paths when you
allow for this in oVirt. In oVirt 3.6, because of this oVirt "two
step", you sometimes ended up with an extraneous path to the storage
domain (not a problem though). And that extra path will go way on
reboot of the nodes.
>
> Regards
> Bernhard
>>
>> On 10/02/2018 05:51 AM, Bernhard Dick wrote:
>>>
>>> Hi,
>>>
>>> I'm trying to achieve iSCSI multipathing with an Dell Compellent
>>> SC4020 array. As the Dell Array does not work as an ALUA system it
>>> displays available LUNs only on the currently active system (here is
>>> a good description that I found:
>>>
https://niktips.wordpress.com/2016/05/16/dell-compellent-is-not-an-alua-s...
>>> ). As a result I cannot add the currently non-active controller to an
>>> iSCSI-Bond (as it does not present the LUNs to oVirt) and so the path
>>> to the second controller will not be up. Is there any way to solve this?
>>>
>>> Regards
>>> Bernhard
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement:
https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
>
https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
>
https://lists.ovirt.org/archives/list/users@ovirt.org/message/GUPFXMI2I5J...
>