Problems with getting FC Target presented..

[kschreyack]

Hi Everyone,

I'm new to FreeNAS 9.3.1, however quickly coming up to speed. The current show stopper for me is presenting storage via FC Target. The card I'm working with is a Qlogic 2462. I've followed the advice here and I have the services and drivers in place that seem to be correct as per the following log output:

freenas isp1: <Qlogic ISP 2432 PCI FC-AL Adapter> port 0xd400-0xd4ff mem 0xfae3c000-0xfae3ffff irq 42 at device 0.1 on pci5
Dec 26 11:23:28 192.168.2.32 Dec 26 11:23:28 nas01 ispfw: registered firmware <isp_2400>


I have the fc adapter in target mode, as per this output (note that isp0 is not plugged in, only isp1):

[root@freenas] ~# grep isp /var/log/messages
Dec 27 09:15:48 freenas ctlfe_onoffline: SIM isp0 (path id 1) target disable succeeded
Dec 27 09:15:48 freenas ctlfe_onoffline: SIM isp1 (path id 2) target disable succeeded
Dec 27 09:15:54 freenas (ctl0:isp0:0:256:0): Target Mode not enabled yet- lun enable deferred
Dec 27 09:15:54 freenas (ctl1:isp0:0:256:1): Target Mode not enabled yet- lun enable deferred
Dec 27 09:15:54 freenas (ctl2:isp0:0:-1:-1): Target Mode not enabled yet- lun enable deferred
Dec 27 09:15:55 freenas ctlfe_onoffline: isp0 current WWNN 0x2000001b328ee2d8
Dec 27 09:15:55 freenas ctlfe_onoffline: isp0 current WWPN 0x2100001b328ee2d8
Dec 27 09:15:55 freenas ctlfe_onoffline: SIM isp0 (path id 1) target enable succeeded
Dec 27 09:15:55 freenas (ctl3:isp1:0:256:0): Target Mode not enabled yet- lun enable deferred
Dec 27 09:15:55 freenas (ctl4:isp1:0:256:1): Target Mode not enabled yet- lun enable deferred
Dec 27 09:15:55 freenas (ctl5:isp1:0:-1:-1): Target Mode not enabled yet- lun enable deferred
Dec 27 09:15:55 freenas ctlfe_onoffline: isp1 current WWNN 0x2000001b32aee2d8
Dec 27 09:15:55 freenas ctlfe_onoffline: isp1 current WWPN 0x2101001b32aee2d8
Dec 27 09:15:56 freenas ctlfe_onoffline: SIM isp1 (path id 2) target enable succeeded

The output above is a result of shutting the FC front end ports and then starting them. They are enabled as follows:

[root@freenas] ~# ctladm port -l
Port Online Frontend Name pp vp
0 YES ioctl ioctl 0 0
1 YES tpc tpc 0 0
2 NO camsim camsim 0 0 naa.5000000402496f03
3 YES camtgt isp0 0 0 naa.2100001b328ee2d8
4 YES camtgt isp1 0 0 naa.2101001b32aee2d8
5 YES iscsi iscsi 257 1 iqn.freenas.myexpertise.net.test01,t,0x0101
6 YES iscsi iscsi 257 2 iqn.freenas.myexpertise.net.test02,t,0x0101

The iscsi stuff works just fine, without any initiator not seeing them. However I have some 4GB fiber that I need to make use of, thus the importance of getting this to work.

Let me know what you think, what info you may need from me in troubleshooting the issue, etc. I thank you, for your help in advance! Have a great day :)

Klaus Schreyack
Systems Engineer
RHCE MCSE A+ Certified

 

[mav@]

Fibre Channel code is under active development now, so I would recommend you to try updating FreeNAS to the latest nightly build, in case this problem could already be fixed. If that won't help, we would need more detailed information about the problem, so I would ask you to set loader tunable "hint.isp.0.debug" to "0x110f", and if that won't be informative may be to "0xffff".

 

[kschreyack]

Hi Mav,

I have changed the train to use the nightly builds, and I've updated FreeNAS using that. Unfortunately, there was no change to the issue. So, I have enabled debug via the tunable you provided. My fiber connection was actually on isp1 so I have now moved the fiber connection to isp0 to match the tunable.

Here is some output that I've noted, since turning down and then up the ports via ctladm:

Dec 29 20:19:30 nas01 isp0: Chan 0 4Gb Fabric (F_Port) PortID 0x0a0300 LoopID 0x00
Dec 29 20:19:30 nas01 isp0: Chan 0 FC link test done
Dec 29 20:19:30 nas01 isp0: Chan 0 FC loop scan
Dec 29 20:19:30 nas01 isp0: Chan 0 FC loop scan done (no loop)
Dec 29 20:19:30 nas01 isp0: Chan 0 FC fabric scan
Dec 29 20:19:30 nas01 isp0: Chan 0 Fabric Nameserver rejected GID_FT (Reason=0x9 Expl=0x7)
Dec 29 20:19:30 nas01 isp0: Chan 0 FC got to Fabric Scan Done state
Dec 29 20:19:30 nas01 isp0: Chan 0 sleep for 1 seconds
Dec 29 20:19:31 nas01 isp0: Chan 0 Checking FC state
Dec 29 20:19:31 nas01 isp0: Chan 0 FC PDB sync
Dec 29 20:19:31 nas01 isp0: Chan 0 [0] WWPN 0x21fd00051e049bb9 PortID 0xfffc0a handle 0x0 (INI,RdXfrDis) stayed
Dec 29 20:19:31 nas01 isp0: Chan 0 FC PDB sync done
Dec 29 20:19:31 nas01 isp0: Chan 0 FC got to Ready state
Dec 29 20:19:31 nas01 isp0: Chan 0 Loop is up
Dec 29 20:19:31 nas01 isp0: Chan 0 sleep for 0 seconds
Dec 29 20:19:31 nas01 isp0: [0x11f944] now sending synthesized status orig_dl=255 xfered=96 bit=0
Dec 29 20:19:31 nas01 isp0: Chan 0 Port Database Changed (nphdl 0x0 state 0x7 reason 0xb)
Dec 29 20:19:31 nas01 isp0: Chan 0 Loop changed
Dec 29 20:19:31 nas01 isp0: Chan 0 WWPN 0x21fd00051e049bb9 PortID 0xfffc0a handle 0x0 vtgt 0 deleted
Dec 29 20:19:31 nas01 isp0: Chan 0 [0] WWPN 0x21fd00051e049bb9 PortID 0xfffc0a handle 0x0 (INI,RdXfrDis) gone zombie
Dec 29 20:19:31 nas01 isp0: Chan 0 Starting Gone Device Timer with 30 seconds time now 6077
Dec 29 20:19:31 nas01 isp0: Chan 0 Checking FC state
Dec 29 20:19:31 nas01 isp0: Chan 0 FC loop scan
Dec 29 20:19:31 nas01 isp0: Chan 0 FC loop scan done (no loop)
Dec 29 20:19:31 nas01 isp0: Chan 0 FC fabric scan
Dec 29 20:19:31 nas01 isp0: Chan 0 Fabric Nameserver rejected GID_FT (Reason=0x9 Expl=0x7)
Dec 29 20:19:31 nas01 isp0: Chan 0 FC got to Fabric Scan Done state
Dec 29 20:19:31 nas01 isp0: Chan 0 sleep for 1 seconds
Dec 29 20:19:32 nas01 isp0: Chan 0 Checking FC state
Dec 29 20:19:32 nas01 isp0: Chan 0 FC PDB sync
Dec 29 20:19:32 nas01 isp0: Chan 0 FC PDB sync done
Dec 29 20:19:32 nas01 isp0: Chan 0 FC got to Ready state
Dec 29 20:19:32 nas01 isp0: Chan 0 Loop is up
Dec 29 20:19:32 nas01 isp0: Chan 0 sleep for 0 seconds
Dec 29 20:20:02 nas01 isp0: Chan 0 [0] PortID 0xfffc0a Departed because of Gone Device Timeout
Dec 29 20:20:02 nas01 ctlfeasync: WWPN 0x21fd00051e049bb9 port 0xfffc0a path 1 target 0 left
Dec 29 20:20:02 nas01 isp0: Chan 0 Stopping Gone Device Timer @ 6108

 

[mav@]

I think you should search for the problem on the FC switch side. In log messages provided I see that 1) switch itself connects to the FreeNAS target to do basic discovery, and it looks working fine, and 2) when FreeNAS requests FC switch about the list of FCP-capable hosts (SCSI initiators and other targets) it receives reply that there are none at all, not even the FreeNAS itself. Combining that I would assume that you may have misconfigured zoning on your FC switch.

 

[kschreyack]

Good call Mav, and thanks. We can consider this closed and solved for.

I had a misconfiguration on the silkworm. It was defined, but the problem showed up when looking at the alias and effective configuration. I created a new configuration and zone for test, and the effective configuration now had port 3 in it - which is the freenas server. I can now see the target from all servers on the switch. Here is what I previously had, and the newly created configuration:

Brocade1:admin> alishow
Defined configuration:
cfg: SANCFG SANa; SANb
zone: SANa 10,1; 10,2; 10,3; 10,4; 10,6
zone: SANb 10,0; 10,1; 10,3; 10,4; 10,6

Effective configuration:
cfg: SANCFG
zone: SANa 10,1
10,2
10,4
10,6
zone: SANb 10,0
10,1
10,4
10,6

Brocade1:admin> alishow
Defined configuration:
cfg: NewZone ZoneAllPort
cfg: SANCFG SANa; SANb
zone: SANa 10,1; 10,2; 10,3; 10,4; 10,6
zone: SANb 10,0; 10,1; 10,3; 10,4; 10,6
zone: ZoneAllPort
10,0; 10,1; 10,2; 10,3; 10,4; 10,5; 10,6; 10,7; 10,8; 10,9;
10,10; 10,11; 10,12; 10,13; 10,14; 10,15

Effective configuration:
cfg: NewZone
zone: ZoneAllPort
10,0
10,1
10,2
10,3
10,4
10,5
10,6
10,7
10,8
10,9
10,10
10,11
10,12
10,13
10,14
10,15

Brocade1:admin>