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

Stephan Budach stephan.budach at JVM.DE
Mon Dec 14 15:46:53 UTC 2015


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

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
>


More information about the OmniOS-discuss mailing list