[parisc-linux] A3308 fibre SCSI bridge support

[parisc-linux] A3308 fibre SCSI bridge support

[Mark R. Buechler]

I recently purchased a SCSI bridge (4/2 A3308) thinking I could use this
with Linux but when I tried I found that it requires a driver. I can see
the MUX and all devices connected to it from an HP workstation with the
MUX driver loaded, but I'd really like to use this from Linux.

I'm wondering if anyone is working on a driver for this device and would
it work with x86 as well?

THanks, Mark.

Re: [parisc-linux] A3308 fibre SCSI bridge support

[Grant Grundler]

On Sun, Dec 29, 2002 at 04:02:38PM -0500, Mark R. Buechler wrote:
> I recently purchased a SCSI bridge (4/2 A3308) thinking I could use this
> with Linux but when I tried I found that it requires a driver. I can see
> the MUX and all devices connected to it from an HP workstation with the
> MUX driver loaded, but I'd really like to use this from Linux.

uhm...did you check to see which utilities you might need to manage
and configure the FC/SCSI mux?
http://www.software.hp.com/products/FCMAN/fcm3over.html

BTW, The A3308 usermanual (A3308-96011) is available here:
	http://www.software.hp.com/products/FCMAN/pdf/96011.pdf

> I'm wondering if anyone is working on a driver for this device and would
> it work with x86 as well?

The main FC HBA vendors (except Agilent?) seem to work fine on both x86 and
ia64 (HP ZX1, near cousin to HP PARISC platforms). I would expect them
to work fine on i386/parisc-linux too. I've only had time to play with
Agilent based (tachlite 5100/5166/5200 series) HBAs on parisc.

AFAICT, "FC 4/2 MUX" is only supported under HPUX.
I get the impression one would need to heavily modify an existing
FC driver in order to support the MUX functionality. But I don't
know how the A3308 presents SCSI devices and that will make/break
the support story.

hth,
grant

RE: [parisc-linux] A3308 fibre SCSI bridge support

[Buechler, Mark R]

Configuring the MUX isn't a problem. What I'd like to do is access the SCSI
devices connected to the MUX from Linux. From a Linux host I see the MUX as
a single target. I wouldn't think any changes would be necessary for the FC
driver but rather a separate driver would exist that scans for the MUX and
uses the Linux sg driver to communicate with it.

I've found mention of a SCSI/MUX driver on this mailing list in the archives
but I don't know what MUX they were referring to.

- Mark.

-----Original Message-----
From: parisc-linux-admin@lists.parisc-linux.org
[mailto:parisc-linux-admin@lists.parisc-linux.org]On Behalf Of Grant
Grundler
Sent: Monday, December 30, 2002 1:45 AM
To: Mark R. Buechler
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] A3308 fibre SCSI bridge support


On Sun, Dec 29, 2002 at 04:02:38PM -0500, Mark R. Buechler wrote:
> I recently purchased a SCSI bridge (4/2 A3308) thinking I could use this
> with Linux but when I tried I found that it requires a driver. I can see
> the MUX and all devices connected to it from an HP workstation with the
> MUX driver loaded, but I'd really like to use this from Linux.

uhm...did you check to see which utilities you might need to manage
and configure the FC/SCSI mux?
http://www.software.hp.com/products/FCMAN/fcm3over.html

BTW, The A3308 usermanual (A3308-96011) is available here:
	http://www.software.hp.com/products/FCMAN/pdf/96011.pdf

> I'm wondering if anyone is working on a driver for this device and would
> it work with x86 as well?

The main FC HBA vendors (except Agilent?) seem to work fine on both x86 and
ia64 (HP ZX1, near cousin to HP PARISC platforms). I would expect them
to work fine on i386/parisc-linux too. I've only had time to play with
Agilent based (tachlite 5100/5166/5200 series) HBAs on parisc.

AFAICT, "FC 4/2 MUX" is only supported under HPUX.
I get the impression one would need to heavily modify an existing
FC driver in order to support the MUX functionality. But I don't
know how the A3308 presents SCSI devices and that will make/break
the support story.

hth,
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux










EMAIL DISCLAIMER 

Please Note: The information contained in this message may be privileged and
confidential, protected from disclosure, and/or intended only for the use of
the individual or entity named above. If the reader of this message is not
the intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
disclosure, distribution, copying or other dissemination of this
communication is strictly prohibited. If you received this communication in
error, please immediately reply to the sender, delete the message and
destroy all copies of it.

Thank You

Re: [parisc-linux] A3308 fibre SCSI bridge support

[Grant Grundler]

On Mon, Dec 30, 2002 at 10:13:24AM -0500, Buechler, Mark R wrote:
> Configuring the MUX isn't a problem.

ok.

> What I'd like to do is access the SCSI
> devices connected to the MUX from Linux. From a Linux host I see the MUX as
> a single target.

Can you copy the output here?
I'm curious how it's reported.

> I wouldn't think any changes would be necessary for the FC
> driver but rather a separate driver would exist that scans for the MUX and
> uses the Linux sg driver to communicate with it.

the sg driver is a passthru interface and doesn't present a "random
access mass storage device" view. sg would be used to configure
the MUX and sd to access the devices behind it.

My point was the existing FC interface drivers already present FC
storage devices (eg disks or arrays) via "sd" driver and don't know how
to talk to devices that aren't "transperent" (ie invisible nodes in the
FC fabric).

RE: [parisc-linux] A3308 fibre SCSI bridge support

[Buechler, Mark R]

The only place it shows up is in /proc/scsi/qla2200/1. The target id is 18
(WWN: 50060b000005cc76 I assume since it starts with "50").

-------------------------------------------------------------

QLogic PCI to Fibre Channel Host Adapter for ISP22xx:
        Firmware version:  2.02.03, Driver version 6.01.00
Entry address = c481a060
HBA: QLA2200 , Serial# B56623
Request Queue = 0x3a2c000, Response Queue = 0x3a34000
Request Queue count= 128, Response Queue count= 64
Total number of active commands = 0
Total number of interrupts = 80
Total number of IOCBs (used/max) = (0/600)
Total number of queued commands = 0
    Device queue depth = 0x10
Number of free request entries = 47
Number of mailbox timeouts = 0
Number of ISP aborts = 0
Number of loop resyncs = 0
Number of retries for empty slots = 0
Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0
Host adapter:loop state= <READY>, flags= 0x8a0a13
Dpc flags = 0x0
MBX flags = 0x0
SRB Free Count = 4096
Port down retry = 008


SCSI Device Information:
scsi-qla1-adapter-node=200000e08b22cf63;
scsi-qla1-adapter-port=210000e08b22cf63;
scsi-qla1-target-0=20000060b02ac26c;
scsi-qla1-target-1=2100002037843e57;
scsi-qla1-target-2=21000020378437c0;
scsi-qla1-target-3=21000004cf0ef21a;
scsi-qla1-target-4=21000004cf2248d0;
scsi-qla1-target-5=210000203784354b;
scsi-qla1-target-6=2100002037669132;
scsi-qla1-target-7=2100002037843560;
scsi-qla1-target-8=2100002037843cd9;
scsi-qla1-target-9=50060b000005d7b3;
scsi-qla1-target-10=210000203784498c;
scsi-qla1-target-11=21000004cf1b3830;
scsi-qla1-target-12=21000004cf2250b5;
scsi-qla1-target-13=2100002037843e36;
scsi-qla1-target-14=2100002037e7184c;
scsi-qla1-target-15=2100002037843c3c;
scsi-qla1-target-16=210000203766907b;
scsi-qla1-target-17=21000020371ac091;
scsi-qla1-target-18=50060b000005cc76;

SCSI LUN Information:
(Id:Lun)
( 1: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:02,
( 2: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:03,
( 3: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:04,
( 4: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:05,
( 5: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:06,
( 6: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:07,
( 7: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:08,
( 8: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:09,
(10: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:0c,
(11: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:0d,
(12: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:0e,
(13: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:0f,
(14: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:10,
(15: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:11,
(16: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:12,
(17: 0): Total reqs 5, Pending reqs 0, flags 0x0, 1:0:13,

-----Original Message-----
From: grundler@dsl2.external.hp.com
[mailto:grundler@dsl2.external.hp.com]
Sent: Monday, December 30, 2002 2:44 PM
To: Buechler, Mark R
Cc: 'parisc-linux@lists.parisc-linux.org'
Subject: Re: [parisc-linux] A3308 fibre SCSI bridge support


On Mon, Dec 30, 2002 at 10:13:24AM -0500, Buechler, Mark R wrote:
> Configuring the MUX isn't a problem.

ok.

> What I'd like to do is access the SCSI
> devices connected to the MUX from Linux. From a Linux host I see the MUX
as
> a single target.

Can you copy the output here?
I'm curious how it's reported.

> I wouldn't think any changes would be necessary for the FC
> driver but rather a separate driver would exist that scans for the MUX and
> uses the Linux sg driver to communicate with it.

the sg driver is a passthru interface and doesn't present a "random
access mass storage device" view. sg would be used to configure
the MUX and sd to access the devices behind it.

My point was the existing FC interface drivers already present FC
storage devices (eg disks or arrays) via "sd" driver and don't know how
to talk to devices that aren't "transperent" (ie invisible nodes in the
FC fabric).










EMAIL DISCLAIMER 

Please Note: The information contained in this message may be privileged and
confidential, protected from disclosure, and/or intended only for the use of
the individual or entity named above. If the reader of this message is not
the intended recipient, or an employee or agent responsible for delivering
this message to the intended recipient, you are hereby notified that any
disclosure, distribution, copying or other dissemination of this
communication is strictly prohibited. If you received this communication in
error, please immediately reply to the sender, delete the message and
destroy all copies of it.

Thank You