ESOS as ISCSI initiator and Multipath

56 views
Skip to first unread message

Mike Masse

unread,
Dec 19, 2022, 2:51:46 PM12/19/22
to esos-users
I'm trying to use ESOS 4.0.12 as an ISCSI initiator to connect to an ISCSI target.  The target provides 4 paths and I have the ISCSI initiator portion working fine on the ESOS box and it survives reboots even.    Even though there is only 1 actual target, the ISCSI initiator see's 4 separate drives due to there being 4 separate paths and this is to be expected without multipath working.   The next step I have been working on is to get multipath working and that is where I'm running into a wall.  

multipath on ESOS keeps saying: udev property missing, and blacklists the iscsi drive(s)

I've tried this out on Centos 8 and have setup up the networking and the ISCSI initiator up identically and then went on to get multipath working without any hassle nor need to do any special settings changes to the default.   I've tried copying the entire multipath config from that machine to the esos machine and no matter what I do it keeps blacklisting the ISCSI drive(s)      

I've also tried using the latest non-production ESOS image from the master repo and get identical behaviour.

Just wondering if anyone else has experienced this and or has a fix or can point me in the right direction?




Mike Masse

unread,
Dec 20, 2022, 5:46:43 PM12/20/22
to esos-users
I was able to resolve it.     One of the internal defaults for multipath is to automatically allow devices that have udev properties SCSI_IDENT_* or ID_WWN, and this seems to work automatically on other OS's I've tried, but for whatever reason udev in ESOS does not have those properties set, so my ISCSI devices kept getting blacklisted.    Since this is an internal multipath default, I couldn't just remove it from the config file either.    I ended up overriding the default udev property it was looking for by telling it to look for ID_SCSI instead which I could see was being used by udev.   By having a different udev property listed in the blacklist_exceptions section, multipath seems to have stopped looking for SCSI_IDENT or ID_WWN and it now works like it should.    The snippet from my multipath.conf file looks like this:

blacklist_exceptions {
     property "ID_SCSI"
}

Ideally it would be good to have udev in ESOS provide the SCSI_IDENT properties like other OS's do since pretty much all multipath documentation seems to expect it as well, but I at least have it working for now.
Reply all
Reply to author
Forward
0 new messages