Skip to contentSkip to conversation

Status of qlogic tcp/ip (fc0) support

DISCUSSION Mario Giammarco 4 participants 14 messages Dec 15, 2003 2 messages not in the archive SCSI

lore
Share & tools
lore

Mario Giammarco

author
#0 lore raw

Hello,
I now have a qlogic 2200 card and I am trying tcp/ip support:

- standard qlogicfc built in kernel seems to not support ip (I heard there is a patch somewhere, is it right?)

- qla drivers 6.00 of qlogic website should support it but I am not able to compile them with IP=1 option (I have tried on kernels 2.4.22 2.4.23)

- qla drivers 8.00 on sourceforge seems to not support it (and they works only on 2.6.0 kernel).

Now I am stuck please help me I need them badly.

Thanks in advance for any help.

Signature · 1 line
Mario Giammarco
#1 lore raw
Quoted 8 lines · Mario Giammarco

Hello,
I now have a qlogic 2200 card and I am trying tcp/ip support:

- standard qlogicfc built in kernel seems to not support ip (I heard there is a patch somewhere, is it right?)

- qla drivers 6.00 of qlogic website should support it but I am not able to compile them with IP=1 option (I have tried on kernels 2.4.22 2.4.23)

Hello, using qla2200 from qlogic is IMHO the good solution.
I've already tested it a few months ago and it worked fine except very poor performance (around 20MB/s with a Qlogic switch despite of no load at all).

You should send your compile errors...

Signature · 6 lines
Fabien SALVI

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
author
#2 lore raw

Il lun, 2003-12-15 alle 12:38, Fabien Salvi ha scritto:

Quoted 5 lines

Hello, using qla2200 from qlogic is IMHO the good solution. I've already tested it a few months ago and it worked fine except very poor performance (around 20MB/s with a Qlogic switch despite of no load at all).

Poor tcp/ip performance or scsi performance?

Quoted 1 line

You should send your compile errors...

Yeah!

Here is the complete log:

BTW: How can I compile drivers into kernel and not as modules? Instructions in drivers are erroneuos (I like a .diff ...)

make IP=1
cc -D__KERNEL__ -DMODULE -Wall -O -g -DUDEBUG -DLINUX -Dlinux -DINTAPI -DEXPORT_SYMTAB -DMODVERSIONS -include /usr/src/linux-2.4/include/linux/modversions.h -I/usr/src/linux-2.4/include -I/usr/src/linux-2.4/include/../drivers/scsi -falign-functions=2 -falign-jumps=2 -falign-loops=2 -Wall -Wstrict-prototypes -fomit-frame-pointer -fno-strength-reduce -pipe -DCONFIG_X86_LOCAL_APIC -fno-strict-aliasing -fno-common -mpreferred-stack-boundary=2
-march=i686 -DFC_IP_SUPPORT -DSHT_HAS_HIGHMEM_IO -c qla2200.c -o
qla2200.o
In file included from qla2200.c:43:
qla2x00.c: In function `qla2x00_process_response_queue':
qla2x00.c:11581: warning: passing arg 2 of `qla2x00_ip_receive' from incompatible pointer type
In file included from qla2200.c:43:
qla2x00.c: In function `qla2x00_register_snn':
qla2x00.c:14640: error: incompatible types in assignment qla2x00.c:14641: error: incompatible types in assignment
In file included from qla2200.c:43:
qla2x00.c: In function `qla2x00_configure_local_loop':
qla2x00.c:16664: error: `list_entry_loop_id' undeclared (first use in this function)
qla2x00.c:16664: error: (Each undeclared identifier is reported only once
qla2x00.c:16664: error: for each function it appears in.)
In file included from qla2x00.c:18823,

                 from qla2200.c:43:

qla_cfg.c: In function `qla2x00_add_portname_to_mp_dev':
qla_cfg.c:1045: warning: comparison is always true due to limited range of data type
qla_cfg.c:1057: warning: comparison is always false due to limited range of data type
In file included from qla2x00.c:18823,

                 from qla2200.c:43:

qla_cfg.c: In function `qla2x00_find_mp_dev_by_id':
qla_cfg.c:3575: warning: comparison is always true due to limited range of data type
In file included from qla2x00.c:18824,

                 from qla2200.c:43:

qla_fo.c: In function `qla2x00_fo_set_lun_data':
qla_fo.c:759: warning: comparison is always false due to limited range of data type
In file included from qla2x00.c:18824,

                 from qla2200.c:43:

qla_fo.c: In function `qla2x00_fo_get_tgt':
qla_fo.c:1135: warning: comparison is always true due to limited range of data type
qla_fo.c:1225: warning: comparison is always true due to limited range of data type
make: *** [qla2200.o] Error 1

Signature · 1 line
Mario Giammarco

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw

Hello, I've CC the email to the list, other people could be interested...

Well, it wasn't very difficult.
After building qla2?00.o with IP option and building qlaip, you just have to load these 2 modules. Then, you can see a new network interface (see ifconfig -a).
You can use it like any ethernet devices...

You may also encounter difficulties related to FC connection between your servers. In my test, I was using Qlogic Sanbox2 switch with broadcasting activated.

Quoted 27 lines · r35157anc3 a écrit:

Hello,

Do you know where I can get instructions on setting up ip for qla? I configured the qla ip drivers. I just can't figure out how to mount after setting it up.

&Leo();

Quoted 19 lines · Fabien Salvi
Quoted 8 lines · Mario Giammarco

Hello,
I now have a qlogic 2200 card and I am trying tcp/ip support:

- standard qlogicfc built in kernel seems to not support ip (I heard there is a patch somewhere, is it right?)

- qla drivers 6.00 of qlogic website should support it but I am not able to compile them with IP=1 option (I have tried on kernels 2.4.22 2.4.23)

Hello, using qla2200 from qlogic is IMHO the good solution.
I've already tested it a few months ago and it worked fine except very poor performance (around 20MB/s with a Qlogic switch despite of no load at all).

You should send your compile errors...

Signature · 6 lines
Fabien SALVI

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#5 lore raw

Thanks very much. I've made it as far as setting up the network devices. I now have fc0 network device and with an internal ip, but I can't figure out how I am supposed to mount it? I can mount it over scsi? What if I am trying to access the fc remotely? I guess I just don't understand, but beyond setting up the qla2xip kernel drivers, the documentation doesn't say much.

&Leo();

Quoted 7 lines · Fabien Salvi

Hello, I've CC the email to the list, other people could be interested...

Well, it wasn't very difficult.
After building qla2?00.o with IP option and building qlaip, you just have to load these 2 modules. Then, you can see a new network interface (see ifconfig -a).
You can use it like any ethernet devices...

Quoted 38 lines

You may also encounter difficulties related to FC connection between your servers. In my test, I was using Qlogic Sanbox2 switch with broadcasting activated.

Quoted 30 lines · r35157anc3 a écrit:

Hello,

Do you know where I can get instructions on setting up ip for qla? I configured the qla ip drivers. I just can't figure out how to mount after setting it up.

&Leo();

Quoted 21 lines · Fabien Salvi
Quoted 9 lines · Mario Giammarco

Hello,
I now have a qlogic 2200 card and I am trying tcp/ip support:

- standard qlogicfc built in kernel seems to not support ip (I heard there is a patch somewhere, is it right?)

- qla drivers 6.00 of qlogic website should support it but I am not able
to compile them with IP=1 option (I have tried on kernels 2.4.22 2.4.23)

Hello, using qla2200 from qlogic is IMHO the good solution.
I've already tested it a few months ago and it worked fine except very poor performance (around 20MB/s with a Qlogic switch despite of no load at all).

You should send your compile errors...

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#6 lore raw

You can communicate with other servers on the same SAN network also using FC-IP.
I don't understand what you mean with "mount" ?
You have nothing to mount, it's a network interface like any other one to use classic IP protocol.

It has nothing to do with iSCSI or something like that...

Quoted 24 lines · r35157anc3 a écrit:

Thanks very much. I've made it as far as setting up the network devices. I now have fc0 network device and with an internal ip, but I can't figure out how I am supposed to mount it? I can mount it over scsi? What if I am trying to access the fc remotely? I guess I just don't understand, but beyond setting up the qla2xip kernel drivers, the documentation doesn't say much.

&Leo();

Quoted 17 lines · Fabien Salvi

Hello, I've CC the email to the list, other people could be interested...

Well, it wasn't very difficult.
After building qla2?00.o with IP option and building qlaip, you just have to load these 2 modules. Then, you can see a new network interface (see ifconfig -a).
You can use it like any ethernet devices...

You may also encounter difficulties related to FC connection between your servers. In my test, I was using Qlogic Sanbox2 switch with broadcasting activated.

Quoted 5 lines · r35157anc3 a écrit:

Hello,

Do you know where I can get instructions on setting up ip for qla? I configured the qla ip drivers. I just can't figure out how to mount after setting it up.

&Leo();

Signature · 6 lines
Fabien SALVI

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#7 lore raw

I've isolated myself from the SAN network and I'm operating in my own private subnet. It's just my server, the FC controller, and a hard drive connected to the controller.

I want to connect to devices interfaced with the FC over IP. I have a hard drive interfaced with a qla 2300 controller. Now that I have the FC setup for IP, how would I mount that disk?

Perhaps I'm going about this all wrong though. I always thought IP was an alternative to SCSI for FC. Usually, I mount my SCSI devices. If I'm not going to use SCSI, then how do I use it if not by mounting?

Thanks for being so helpful,
&Leo();

Quoted 4 lines · Fabien Salvi

You can communicate with other servers on the same SAN network also using FC-IP.
I don't understand what you mean with "mount" ?
You have nothing to mount, it's a network interface like any other one to use classic IP protocol.

Quoted 32 lines

It has nothing to do with iSCSI or something like that...

Quoted 25 lines · r35157anc3 a écrit:

Thanks very much. I've made it as far as setting up the network devices. I now have fc0 network device and with an internal ip, but I can't figure out how I am supposed to mount it? I can mount it over scsi? What if I am trying to access the fc remotely? I guess I just don't understand, but beyond setting up the qla2xip kernel drivers, the documentation doesn't say much.

&Leo();

Quoted 18 lines · Fabien Salvi

Hello, I've CC the email to the list, other people could be interested...

Well, it wasn't very difficult.
After building qla2?00.o with IP option and building qlaip, you just have to load these 2 modules. Then, you can see a new network interface (see ifconfig -a).
You can use it like any ethernet devices...

You may also encounter difficulties related to FC connection between your servers. In my test, I was using Qlogic Sanbox2 switch with broadcasting activated.

Quoted 5 lines · r35157anc3 a écrit:

Hello,

Do you know where I can get instructions on setting up ip for qla? I configured the qla ip drivers. I just can't figure out how to mount after setting it up.

&Leo();

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#8 lore raw
Quoted 5 lines · r35157anc3 a écrit:

I've isolated myself from the SAN network and I'm operating in my own private subnet. It's just my server, the FC controller, and a hard drive connected to the controller.

I want to connect to devices interfaced with the FC over IP. I have a hard drive interfaced with a qla 2300 controller. Now that I have the FC setup for IP, how would I mount that disk?

Perhaps I'm going about this all wrong though.

Yes !
You can't mount devices using IP over FC.
You can only access other FC nodes (essentially servers) that also have IP over FC activated.
It could be useful for example to share storage over NFS in a cluster connected to the same SAN, because there are not many Shared FileSystem (except GFS but it's no longer GPL...).

Quoted 1 line

I always thought IP was an alternative to SCSI for FC. Usually, I mount my SCSI devices. If I'm not going to use SCSI, then how do I use it if not by mounting?

No, you won't be able to mount your SCSI devices.
If you want to this, use SCSI over FC, it's the traditionnal way to do it. You *really* have no interest, even it would be possible, to use IP to mount SCSI devices...

Signature · 6 lines
Fabien SALVI

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): [email protected]

#10 lore raw
Quoted 2 lines · r35157anc3 a écrit:

So, IP over FC essentially lets you use your FC as a NIC? Am I right?

Exactly ! It's the same as you would have if you connect your servers with Gigabit NIC to a Gigabit Ethernet Switch...

Signature · 6 lines
Fabien SALVI

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#11 lore raw

I recently read an article on iSCSI and FCIP. That's what initially got me interested in this. I think this is actually what I'm wanting to do here. Do you know if the qla 2300 HBA is capable of iSCSI? Is there a linux driver for iSCSI or any plans for one?

&Leo();

Quoted 10 lines · Fabien Salvi
Quoted 2 lines · r35157anc3 a écrit:

So, IP over FC essentially lets you use your FC as a NIC? Am I right?

Exactly ! It's the same as you would have if you connect your servers with Gigabit NIC to a Gigabit Ethernet Switch...

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#12 lore raw
Quoted 4 lines

I recently read an article on iSCSI and FCIP. That's what initially got me interested in this. I think this is actually what I'm wanting to do here. Do you know if the qla 2300 HBA is capable of iSCSI?

No, the 2xxx series HBAs are *not* iSCSI HBAs. QLogic does make iSCSI HBAs (the 4xxx series cards), info at qlogic.com.

Quoted 3 lines

Is there a
linux driver for iSCSI or any plans for one?

For the 4xxx series HBAs, yes.

Regards,
Andrew Vasquez

author
#13 lore raw
In reply to Fabien Salvi

Il lun, 2003-12-15 alle 12:38, Fabien Salvi ha scritto:

Quoted 1 line

You should send your compile errors...

I am getting crazy.

I have tried with 2.4.18 2.4.22 2.4.23 2.6.0-test11 and I was not able to compile it.

What am I doing wrong?

#14 lore raw
Quoted 8 lines · Mario Giammarco
Quoted 1 line

You should send your compile errors...

I am getting crazy.

I have tried with 2.4.18 2.4.22 2.4.23 2.6.0-test11 and I was not able to compile it.

What am I doing wrong?

Try the attached patch against 6.06.10 (available from the QLogic website).

Regards,
Andrew Vasquez

qla2x00.c renamed from drv/qla2x00.c +8 -4
diff -Nurd 60610-dist/drv/qla2x00.c 60610-ip1/qla2x00.c
@@ -11578,7 +11578,7 @@
 
 			case ET_IP_RECEIVE:
 				/* Handle IP receive packet */
-				qla2x00_ip_receive(ha, pkt);
+				qla2x00_ip_receive(ha, (response_t *)pkt);
 				break;
 
 			case ET_MAILBOX_COMMAND:

@@ -14637,8 +14637,8 @@
 
 	/* Prepare CT request */
 	ct_iu = (struct ct_sns_pkt *)ha->ct_iu;
-	ct_req = ct_iu->p.req;
-	ct_rsp = ct_iu->p.rsp;
+	ct_req = &ct_iu->p.req;
+	ct_rsp = &ct_iu->p.rsp;
 
 	/* Initialize Name Server CT-Command header */
 	qla2x00_prep_nsrv_ct_cmd_hdr(ct_req,RSNN_NN_CMD,RSNN_NN_RSP_SIZE);

@@ -16607,10 +16607,14 @@
 	for ( ; size >= sizeof(port_list_entry_t);
 			size -= sizeof(port_list_entry_t),
 			port_entry++) {
+#if defined(FC_IP_SUPPORT)
+		uint16_t list_entry_loop_id;
+#endif
 		device.loop_id = le16_to_cpu(port_entry->loop_id);
 
 #if defined(FC_IP_SUPPORT)
-		device.loop_id &= LOOP_ID_MASK; 
+		list_entry_loop_id = port_entry->loop_id;
+		port_entry->loop_id &= LOOP_ID_MASK; 
 #endif
 
 		/* Skip any non-local loop-ids - this includes 'known ports' */
qla2x00.h renamed from drv/qla2x00.h +0 -1
diff -Nurd 60610-dist/drv/qla2x00.h 60610-ip1/qla2x00.h
@@ -2954,7 +2954,6 @@
 
 #define PORT_SCAN_NEEDED      28      /* */
 #define IOCTL_ERROR_RECOVERY	29      
-#define FDMI_REGISTER_NEEDED	30
 
 
 /* macro for timer to start dpc for handling mailbox commands */
author
#15 lore raw

Il lun, 2003-12-15 alle 19:19, Andrew Vasquez ha scritto:

Quoted 3 lines

Try the attached patch against 6.06.10 (available from the QLogic website).

Thank you very much! It almost works now!
BTW: I checked again qlogic website and I have not found it...
BTW2: About iSCSI. There are several software iscsi initiator and target for linux (search with google and in sourceforge). I suggest ardis target and cisco initiator. They are completely software so they run on every tcp/ip based network. I have tested them on ethernet but they should run also on fc0. But they are completely software based: they use fibre channel only like a fast ethernet.

AND NOW the big problem:

I try to ping from qlogic card to mpt-fusion (lsi logic) card and viceversa.

Hardware works (both cards see my fibre channel hard disks)

All packets are lost (destination host unreachable), route is ok.

On qlogic based host I see in dmesg output:

qla2x00_send_packet: Unable to determine loop id for destination.
qla2200ip: fc0 - Unable to send packet -- Bad error occured!!!
qla2x00_send_packet: Unable to determine loop id for destination.
qla2200ip: fc0 - Unable to send packet -- Bad error occured!!!
qla2x00_send_packet: Unable to determine loop id for destination.
qla2200ip: fc0 - Unable to send packet -- Bad error occured!!!
...
...

I suppose the bug is perhaps in mpt-fusion code because I triggered it also with two lsi logic cards.

Please tell it to lsi logic developers also!

Thanks again for past and future help!

Signature · 1 line
Mario Giammarco