So you want to test FC target mode?

[aufalien]

First and foremost your iSCSI config must be in order or else this won't work. So if its not starting, check why and fix.

Also, you need to debug this, look at your console during boot or check the messages log file looking for lines relating to isp etc...

While my QLE 2460 (4Gb) worked off the bat, my QLE2560 (8Gb) didn't and I had to add ispfw_load="YES" in the loader.conf file.

In terms of seeing it, if your target is set up proper, then client machine (initiator) should see it as a block device, no diff then a discreet disk.

I assumed you checked your FC HBA link lights to see weather they light up etc...

 

[Gerasim]

in freenas console i get
"isp0 unknown CTIO7 status 0x0 "
links exist green ..4 gb.
fc qlogic card of server freenas was connect to fc switch emc2 ds 4400m

i meen about load module that

mount -u -w /
cd /tmp
fetch http://people.freebsd.org/~delphij/misc/ispfw.ko.xz
unxz ispfw.ko.xz
install -m 555 ispfw.ko /boot/kernel

and i'll use a FreeNAS-9.2.1.7-RELEASE-x64 (fdbe9a0)
tonight i'll tri to upgrade to FreeNAS-9.3-ALPHA-d5b165e-x64.iso

 

[aufalien]

Hmm, so you are not using 9.2.1.7? Well I'd suggest that and ditch loading the module.

So looks like your FC is in order as is your iSCSI.

Hopefully 9.2.1.7 works for you as thats what I'm on. The latest 9.3 also works, you still need to apply JPs loader.conf mods though. And don;t forget the post init script, very important.

 

[Gerasim]

damn %)) i am use 9.2.7.1 %))
sorry for my english
what mod are you saying?

you about

1. # mountrw / && sed -i "" -e 's/\(role\)=2/\1=1/' /boot/loader.conf && mount -ur /

that? after upgrade to 9.3.alpha?

 

[aufalien]

The one at the top of this thread.

- Mod /boot/loader.conf changing all role=2 lines to role=1 (near the bottom of the file).
- Create a postinit script that runs /usr/sbin/ctladm port -o on
- In the iSCSI settings check the box for enable experimental target mode. (this will trip a reboot)

 

[Gerasim]

can you please provide me about postinit script? where i must put it an what a content must be?

 

[aufalien]

Read the manual page 63-64.

I've said it before, its a damn fine manual.

http://web.freenas.org/images/resources/freenas9.2.1/freenas9.2.1_guide.pdf

 

[Gerasim]

AAAA!!! sorry for caps! but i did it!! postinit script and mod of loader with 9.3 freenas and i'll get 2.4 tb of storage that present and best performance for esxi !
my conf is proliant g5 with p800i raid controller with two hp msa50 with 20 sas disk of 146 gb.... it's cool!!
Aufalien !!! Thank you really!! and of couse topickstarter!!

p/s/ ip config now is dhcp.... i thoughts i must set it manualy...

 

[Gerasim]

btw... connection with esxi going through fiber or ethernet? my freenas was connect to uplink... and one fc to fabrick switch

 

[aufalien]

You mean for FC target, fiber of course. I'm unsure weather FCoE would even work in this case or what implications iSCSI would have on it.

FC target mode is just that, Fibre Channel over its traditional layer 2 medium being fiber.

 

[Gerasim]

but iscsi target was made and it represent as fc target on fiber and not by ethernet..? even if ethernet uplink was disconnected... change dhcp ip address? (i understand that must to conf manualy but in case...

 

[aufalien]

Sure, that's how I have mine set. That's what FC target mode is all about. Keep in mind this is a revolving/evolving solution. The devs are still integrating FC target into a proper UI setting.

 

[nickm]

Sure, that's how I have mine set. That's what FC target mode is all about. Keep in mind this is a revolving/evolving solution. The devs are still integrating FC target into a proper UI setting.

So i've subscribed to the thread, hoping that someone would be able to figure out how FC in freenas works, so they could enlighten the rest of us, but there's still no eureka moment. I know you keep saying 'follow the first post!', but there are no instructions in the first post, nor is it clear in any post what to do after setting the HBA to target mode.

Let me give you an example of what things are supposed to look like, and what things generally happen next on a storage system with an FC target. This is using OmniOS (Solaris with COMSTAR).

stmfadm list-target -v

Target: iqn.2012-12.com.home:micro

Operational Status: Online
Provider Name : iscsit
Alias : micro
Protocol : iSCSI
Sessions : 0​

Target: wwn.2101001B32A2CAC4

Operational Status: Online
Provider Name : qlt
Alias : qlt1,0
Protocol : Fibre Channel
Sessions : 4

Initiator: wwn.2100001B32115326

Alias: QLE2460 FW:v7.01.00 DVR:v1.1.20.0
Logged in since: Mon Aug 25 04:59:34 2014​

Initiator: wwn.2100001B32019057

Alias: QLE2460 FW:v7.01.00 DVR:v1.1.20.0
Logged in since: Mon Aug 25 04:59:33 2014​

Initiator: wwn.2100001B321044CF

Alias: QLE2460 FW:v7.03.00 DVR:v9.1.11.28
Logged in since: Mon Aug 25 04:59:33 2014​

Initiator: wwn.2100001B321CE19D

Alias: QLE2460 FW:v7.00.02 DVR:v9.1.11.24
Logged in since: Mon Aug 25 04:59:33 2014​

Target: wwn.2100001B3282CAC4

Operational Status: Online
Provider Name : qlt
Alias : qlt0,0
Protocol : Fibre Channel
Sessions : 4
Initiator: wwn.2100001B32115326

Alias: QLE2460 FW:v7.01.00 DVR:v1.1.20.0
Logged in since: Mon Aug 25 04:59:34 2014​

Initiator: wwn.2100001B32019057

Alias: QLE2460 FW:v7.01.00 DVR:v1.1.20.0
Logged in since: Mon Aug 25 04:59:33 2014​

Initiator: wwn.2100001B321044CF

Alias: QLE2460 FW:v7.03.00 DVR:v9.1.11.28
Logged in since: Mon Aug 25 04:59:33 2014​

Initiator: wwn.2100001B321CE19D

Alias: QLE2460 FW:v7.00.02 DVR:v9.1.11.24
Logged in since: Mon Aug 25 04:59:33 2014​

So in this command output from 'stmfadm list-target -v' i get both iscsi target and fc target. You can also see each initiator that is trying to come into each FC target because i already have my VSANs, zonesets, and zones set up on my fabric.

Now from within OmniOS (or Solaris), all i need to do is create device-extents for my zvols, which will get them naa.<guid> identifiers, create host-groups, which will allow those wwn.<hba wwn> initiators to be mapped to a logical group, then create the relationship between host-group and extent.

The zvol extent can be mapped either or to wwn.<hba wwn> initiator type, or to an iscsi initiator, which has the iqn.<initiator> prefix, and there's a consistent set of naming, mapping, and masking.

Someone needs to explain step by step how initiators log in when making these changes in FreeNAS, how to map WWPN initiators to groups, and how to handle the end-to-end fiber-channel mapping (assuming you have a 1host-to-1target fabric zone set up.

 

[Gerasim]

dude! firts of all prepare raid or disk you want to present as fs target, next try to install clean alpha 9.3 version on comp or server you want to use as freenas fc target. also make iscsi target/initiator/portal/exten and enable iscsi service. third - connect fc card to witch or you fabric.. fourth configure static ip of you nic and in shell do command:
" mountrw / && sed -i "" -e 's/\(role\)=2/\1=1/' /boot/loader.conf && mount -ur / " without first and last quotes.
Last one you must make postinit script to enable fc target. /usb/sbin/ctladm port -o.
of couse if you use fabri you must zonning fc wwn:wwp on it.
in my case whole of esxi who connect to my switch was seen my freenas lun

 

[aufalien]

Well, I actually said follow the manual in setting up iSCSI and then follow this (JPs) initial post. I use an FC switch with several clients and have no zoning due to the nature of my env. being an XSAN.

I'm running 9.2.1.7 no issues.

Also JP even said;

"When the system comes back up any targets you've set up for iSCSI will show up as FC targets as well. Make sure not to use them via both access methods at the same time!".

BTW, I thought it pertinent to mention that my SAN clients are all in the default zone so there is no real zoning going on. Kind of like a layer 2 switch having no VLAN config when in fact all switch ports are in a default VLAN.

HTH.

 

[Nem0]

Freenas 9.3-M3
------------------
Many thanks for excellent job guys!
With freenas i was able to have much more diskspace to our Oracle DB on AIX powerd PS702 Blades without buying to expensive branded SAN storage. iSCSI and FC connetction work as expected. Many thanks again.

But how about:
1. Extents created on a devices ( arrays on Adaptec's 5x controllers ) after initialising - becomes second incarntion as a standard bsd disks like daX. How about disabling this behavoir? But FreeNAS complains about corrupted GPT

2. LUN masking. It's possible? Auth groups works on a IP basis, and couldn't help with FC connections.

I'l try to write simple report later this month

 

[mav@]

1. Extents created on a devices ( arrays on Adaptec's 5x controllers ) after initialising - becomes second incarntion as a standard bsd disks like daX. How about disabling this behavoir?

That is probably consequence of enabling "camsim" CTL port, which purpose is exactly to provide local access to CTL LUNs. Instead of enabling all CTL ports with `ctladm port -o on` command you should do it only for FibreChannel ports with `ctladm port -o on -t fc`.

 

[Johnson]

Anyone try this with the 9.3 Release?

 

[mav@]

I know people who tried. Successfully.

 

[X7JAY7X]

I have FC working with 9.3 stable following the first two steps only in the original post from this thread. I currently have two FC cards in my FreeNAS box going to two ESXi hosts. I have several more ESXi boxes to connect though. Instead of getting a fiber switch, can I just load up the FreeNAS box with many FC cards and go point to point to all the ESXi hosts? How many FC cards does FreeNAS support?