[ovirt-users] iSCSI question... LUNS->Targets balnk

Alan Murrell lists at murrell.ca
Sun Aug 16 20:54:51 UTC 2015


Hi Maor,

It is/was probably something really weird with my 
single-server/self-hosted engine.  As a test I was able to install oVirt 
Node 3.5 on another machine that I could borrow for a short period, and 
I was able to get it connected via iSCSI to my FreeNAS VM, so I am 
satisfied (for my own info) that iSCSI connectivity does work (I didn't 
*really* doubt it since others are using it; I was just a bit frustrated 
on my last post)

That being said, I think there is something odd/weird when trying to use 
iSCSI on a single server/self-hosted engine setup, from which the iSCSI 
connection is also being served from (even from a VM)

In the case of the FreeNAS test, I had the "initiator" set to "ALL", 
meaning any and all IQNs would be allowed to connect.  I didn;t do 
anything different on the FreeNAS side of things, and the oVirt 3.5 Node 
that I installed was able to connect without any issue whatsoever.

I will try the steps you suggest if/when I ever decide to try this 
again, but probably for a setup such as what I am testing, I will 
probably stick to the "local" NFS storage (not yet sure if I will go 
with or without gluster; doing so sort of gives me more felxability in 
the future)


Regards,

Alan



On 16/08/2015 5:24 AM, Maor Lipchuk wrote:
> Hi Alan,
>
> basically, it could be that your ACL in your iSCSI server might be configured without the Initiator IQN of your Host.
> do you have any access to your iSCSI server?
> also, can u try to connect to the iSCSI server directly from your Host and see if it works:
>
> 1) First discover the targets:
>   iscsiadm -m discovery -t st -p {scsi_server_ip},{port}
>
> 2) Try to log out from the target you were trying to login before:
> Example:
>    iscsiadm -m node -u -T {iqn.2015-07.com.target_name.redhat}:{port} -p {scsi_server_ip},{port} -u
>
> 3) list your files at /sys/block
>
> 4) logging in to the target:
>     iscsiadm -m node -T {iqn.2015-07.com.target_name.redhat}:{port} -p {scsi_server_ip},{port} -l
>
> 5) list again all your files at /sys/block, and check if there were new added block devices.
>
>
>
> Regards,
> Maor
>
>
>
> ----- Original Message -----
>> From: "Alan Murrell" <lists at murrell.ca>
>> To: "users" <users at ovirt.org>
>> Sent: Tuesday, August 11, 2015 8:41:24 AM
>> Subject: Re: [ovirt-users] iSCSI question... LUNS->Targets balnk
>>
>> I think it is something with oVirt.  I installed a VM with FreeNAS and
>> configured it tot he setup guide for iSCSI.  Once again, I can connect
>> my Windows 7 PC to the iSCSI target and LUN no problem, but when I try
>> to add iSCSI storage in oVirt, it sees the target, can log in to the
>> target but does not see any LUNs.
>>
>> iSCSI is not a huge deal; I guess I will just stick with NFS and
>> consider iSCSI in oVirt not ready.
>>
>> Regards,
>>
>> Alan
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>




More information about the Users mailing list