[OmniOS-discuss] Ang: Re: How to configure FCoE target in OmniOS?

[Stephan Budach]

Hi Johan,

Am 14.12.15 um 17:26 schrieb Johan Kragsterman:
> Hi!
>
> Is there a question in this mail I miss somewhere...?
well, not in that post, but in the first one, where I asked, if anyone 
would spot some obvious errors in my attempt to configure a FCoE target 
in OmniOS.

>
> Anyway, check further down...
>
>
>
> -----"OmniOS-discuss" <omnios-discuss-bounces at lists.omniti.com> skrev: -----
> Till: Dan McDonald <danmcd at omniti.com>
> Från: Stephan Budach
> Sänt av: "OmniOS-discuss"
> Datum: 2015-12-14 16:48
> Kopia: omnios-discuss <omnios-discuss at lists.omniti.com>
> Ärende: Re: [OmniOS-discuss] How to configure FCoE target in OmniOS?
>
> Well… creating a view, requires a LUN, doesn't it? But anyway, I do have
> some LUNs configured already, which I formerly presented using iSCSI.
> The one I chose for my FCoE testing is this one:
>
> stmfadm list-lu -v
> LU Name: 600144F07A34AC66000054D1DEB50001
>       Operational Status: Online
>       Provider Name     : sbd
>       Alias             : /dev/zvol/rdsk/sasTank/nfsvmpool03sas
>       View Entry Count  : 1
>       Data File         : /dev/zvol/rdsk/sasTank/nfsvmpool03sas
>       Meta File         : not set
>       Size              : 1342177280000
>       Block Size        : 512
>       Management URL    : not set
>       Vendor ID         : SUN
>       Product ID        : COMSTAR
>       Serial Num        : not set
>       Write Protect     : Disabled
>       Writeback Cache   : Disabled
>       Access State      : Active
>
> Thanks,
> Stephan
>
>
>
> Have you enabled the: svcadm enable svc:/system/fcoe_target:default  ?
Yes.
>
> What I remember(years ago I did this...), FCoE HBA's show up when you run: stmfadm list-target (-v for verbose). From there you can get the wwnn and wwpn, which you need to configure fcoe ports:
>
> # fcadm create-fcoe-port -i -p Port_WWN -n Node_WWN Ethernet_Interface
Yeah, I did that as well, but the port actually doesn't seem to login to 
the fabric on the switch. Shouldn't I see some flogi message from the 
target port on th4 switch as well?
>
> Then, if you connect the FCoE initiator to the fabric, and search for a LUN, you will see that if you again run:
>
> stmfadm list-target -v
>
> as a logged in initiator, and from there you will get the wwn on the initiator.
>
> With that info you can create the view for the LUN, for the initiator to be able to access it.
>
> Hope this is the right working order, it was a long time ago I did this...
>
> Regards Johan
>
>
> Am 14.12.15 um 16:35 schrieb Dan McDonald:
>>> On Dec 14, 2015, at 10:25 AM, Stephan Budach <stephan.budach at JVM.DE> wrote:
>>>
>>> Hi guys,
>>>
>>> I am trying to configure a FCoE target in OmniOS r016, but I seem to cannot get it right. I started out with the documentation for Solaris 11, which seemd appropriate and configured a fc target and added a view, which granted the fcoe port access to that LUN, but the ort doesn't seem to login to my Nexus 5500 at all.
>>>
>>> This is what I got so far:
>>>
>>> I was able to successfully connect my Linux FCoE initiator to the fabric, but not the OmniOS target. Is there anything obvious wrong with my config?
>> Do you have any LUs configured?
>>
>> stmfadm list-lu
>>
>> You may want to make sure you have at least one.  Create a ZFS volume and then add it:
>>
>> zfs create -V poolname/volname
>>
>> stmfadm create-lu /dev/zvol/dsk/poolname/volname
>>
>> Dan
>>
> _______________________________________________
>