Hi Kristof, comments inline:

kristof wrote:
> Today I tried to setup a comstar iscsi target.
>
> - I updated my opensolaris 2008.11 to build 105.
> - disabled iscsitgtd
> - installed SUNWiscsit pkg
> - enabled stmf
>
> Then I checked the docs, and there is still 1 thing I  don't understand.
>
> The admin guide says, to create a target run:
>
> itadm create-target
>
> So I did, this was the response:
>
> Target iqn.1986-03.com.sun:02:4b60173a-25c8-44eb-f307-efce316df001 
> successfully created
>
> Then I had to create the LU:
>
> sbdadm create-lu /dev/zvol/rdsk/storagepoolb/vista 
>
> Created the following LU:
>
>               GUID                    DATA SIZE           SOURCE
> --------------------------------  -------------------  ----------------
> 600144f075a6410000004977b0b30003      26843480064      
> /dev/zvol/rdsk/storagepoolb/vista
>
> Next step was to create the view:
>
> (to make a logical unit available to all initiator hosts on a storage network)
>
> stmfadm list-view -l 600144F077000000000048C62BF00001
> stmfadm: 600144f077000000000048c62bf00001: no views found
> -bash-3.2# stmfadm add-view 600144f077000000000048c62bf00001
>
> But what happens when I create multiple targets at once, How can someone find 
> out which target (iqn) is mapped to which LU ?? I don't see the link when we 
> don't create host groups. 
>
> (In the past you saw this mapping via iscsitadm list target -v)
>   

In the COMSTAR model the iSCSI target port that you create is just an 
access point that gets associated with luns through view entries.  If 
you create a completely open view entry for a lun "stmfadm add-view 
<guid>" then the lun is mapped to all ports (all iSCSI target ports 
created with itadm, all FC ports, ...).

> Anyway I tried to connect from a windows initiator and the disk was connected 
> (directly after discovering, I even did not had to choose the target), so it 
> seems to work. 
>
> Then I tried to boot from this exposed volume, via gpxe. For some reason this 
> is not working (I'm getting input/Output Error). Using snoop to capture the 
> packets, I see I'm getting: Check Condition as response to a Read 
> Capacity(10) request. I attached the snoop file so people can look into.
>
> Thanks in advance for any response.
>
> Kristof
>   

Unfortunately wireshark doesn't read snoop traces anymore (anyone know 
why they did this?)  Do you happen to know the sense key, asc and ascq 
from the check condition?

-Peter

_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss

Reply via email to