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

[Johan Kragsterman]

Hi!


-----"OmniOS-discuss" <omnios-discuss-bounces at lists.omniti.com> skrev: -----
Till: <omnios-discuss at lists.omniti.com>
Från: Stephan Budach 
Sänt av: "OmniOS-discuss" 
Datum: 2015-12-15 08:58
Ärende: Re: [OmniOS-discuss] Ang: Re: Ang: Re: How to configure FCoE target in OmniOS?

Am 15.12.15 um 06:55 schrieb Stephan Budach:
> Hi Johan,
>
> Am 14.12.15 um 23:37 schrieb Johan Kragsterman:
>> Hi!
>>
>>
>> -----Stephan Budach <stephan.budach at jvm.de> skrev: -----
>> Till: Johan Kragsterman <johan.kragsterman at capvert.se>
>> Från: Stephan Budach <stephan.budach at jvm.de>
>> Datum: 2015-12-14 19:57
>> Kopia: Dan McDonald <danmcd at omniti.com>, omnios-discuss 
>> <omnios-discuss at lists.omniti.com>
>> Ärende: Re: Ang: Re: [OmniOS-discuss] How to configure FCoE target in 
>> OmniOS?
>>
>>
>>> 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?
>> Yeah, it must register with the name services on the switch, if I 
>> remember correctly. Must be the same as with fibre channel, the name 
>> services must pick it up to be able to serve the name further on to 
>> the SAN.
>>
>> The problem with FCoE is, imho, that the adaptors doesn't have any 
>> bios to check. In FC you go inte the bios and check the presence of 
>> storage devices, I don't think you got that possibility in FCoE 
>> adaptors, do you? But can you perhaps bypass the switch, and see if 
>> you can pick up any device directly?
> Hmm, no… I want to use OmniOS as a FCoE target, actually, not an 
> initiator. I got my FCoE initiator on RHEL already set up and logged 
> in to the fabric. I am wondering a bit about the DCB client though - I 
> am still not sure, if the X520-T2 has one built it or not. On RHEL I 
> configred the DCB_REQUIRED to no and it obviously works, which led me 
> to believe that these Intel CNAs actually do have a DCB client built in.
>>
>> By the way, what kind of switch do you use? I know there are FCoE 
>> switches that have different FCoE ports and FC ports...I mean, if you 
>> confused those ports...?
> I am using a Nexus 5596, with some fabric extenders and although I am 
> pretty sure, that I configured the ports correctly I will check that 
> one again and see, if I made some mistake.
>>
>> Rgrds Johan
> Thanks,
> Stephan 

I think that I do need the LLDP package installed, which will give me 
the DCBX capabilities, I seem to be missing, but actually I can't find 
any package providing that. Does anyone know, where that sucker hides 
in? Or what the equivalent in OmniOS is?

Thanks,
Stephan




Now I remember that Gea(Günther Alka) @ napp-it has FCoE working on his napp-it server. He uses omnios as a base. He's on this list frequently.

Otherwise:

http://napp-it.org/
gea at napp-it.org
alka at hfg-gmuend.de

Regards Johan
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss at lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss