Thanks, William -

Back in March 2005, I had been fighting with LSILogic's version of the
QLogic card, supposedly compatible with Solaris.  After fighting with
it for a month (backups had been 99% completing and then failing due
to a rewind due to an "external condition".  After a month of fighting
with a 3rd-party product, I wasn't taking any more chances and we
replaced the LSILogic's cards with the Sun part.

It was with the Sun part that I found out issues with the QLA2310 driver
(they weren't loading at boot).  I then learned that the Sun cards required
the drivers in the SUNWqlc and SUNWqlcx, and because I was also doing
disk-storage-based backups, I also loaded the SAN_4.4.4 suite of packages.

On Thu, 18 Aug 2005 william.d.brown AT GSK DOT com wrote:

> Date: Thu, 18 Aug 2005 11:24:15 +0100
> From: william.d.brown AT GSK DOT com
> To: Kathryn Hemness <kfhemness AT ucdavis DOT edu>
> Cc: jpiszcz AT servervault DOT com, veritas-bu AT mailman.eng.auburn DOT edu,
>      veritas-bu-admin AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Re:Help moving LTO2 drives onto new QLogic 2342
>     Dual Port Fiber Cards on a Sun V440 running Solaris 8
>
> I'm using a qla2342 in an e220r without problems.
>
> As I want to use the qla2300 driver I did have to edit
> \etc\driver_aliases.  It is well documented on the HP web site, as the
> card I'm using is an HP OEM version of the card.  A google search should
> find the procedure.
>
> Broadly I used prtconf -vp, looked for the fibre channel entries.  There
> is a line with 'compatible' and the entries there indicate what are the
> entries in /etc/driver_aliases that the card will match.   I just made an
> entry for pci1077,2312
>
> qla2300 "pci1077,2312"
>
> That then attached the qla2300 driver.
>
> William D L Brown
>
>
>
>
> "Kathryn Hemness" <kfhemness AT ucdavis DOT edu>
> Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
> 17-Aug-2005 18:32
>
> To
> veritas-bu AT mailman.eng.auburn DOT edu
> cc
> jpiszcz AT servervault DOT com
> Subject
> [Veritas-bu] Re:Help moving LTO2 drives onto new QLogic 2342 Dual Port
> Fiber Cards on a Sun V440 running Solaris 8
>
>
>
>
>
>
> Hi Justin -
>
> I learned via trial-and-error in March that just any QLogic card will not
> work in a Sun server; you need the Sun QLogic FC card for your server.
>
> > Message: 2
> > Date: Wed, 17 Aug 2005 12:36:57 -0400
> > From: "Piszcz, Justin" <jpiszcz AT servervault DOT com>
> > To: <veritas-bu AT mailman.eng.auburn DOT edu>
> > Subject: [Veritas-bu] Help moving LTO2 drives onto new QLogic 2342 Dual
> Port Fiber Cards on a Sun V440 running Solaris 8
> >
> > This is a multi-part message in MIME format.
> >
> > ------_=_NextPart_001_01C5A349.E29264EF
> > Content-Type: text/plain;
> >                charset="us-ascii"
> > Content-Transfer-Encoding: quoted-printable
> >
> > The machine: A Sun V440 running Solaris 8.
> >
> > Note: There is no switch involved.
> >
> > =20
> >
> > DRIVE1 <-> HBA1 PORT 1
> >
> > DRIVE2 <-> HBA1 PORT 2
> >
> > DRIVE3 <-> HBA2 PORT 1
> >
> > DRIVE4 <-> HBA2 PORT 2
> >
> > =20
> >
> > =20
> >
> > My old configuration:
> >
> > =20
> >
> > Using JNI-1063 & JNI-6410 cards, I plug four LTO2 drives directly into
> > three JNI-1063 cards and one JNI-6410 card.
> >
> > =20
> >
> > =20
> >
> > My new configuration:
> >
> > =20
> >
> > Two 2300 (2342) based cards dual port gigabit Ethernet.
> >
> > =20
> >
> > =20
> >
> > I removed the old drivers and installed the QL2300 driver, the QL2300
> > driver is one of three drivers.  The Sun QLC and QLCX drivers are
> > included in Solaris 8.
> >
> > =20
> >
> > =20
> >
> > In my dmesg, I clearly see the devices available, as shown below:
> >
> > =20
> >
> > Aug 17 14:01:07 backup01 scsi: [ID 365881 kern.info]
> > /pci@1d,700000/SUNW,qlc@2/fp@0,0/st@w50060b00002047f0,0 (st60):
> >
> > Aug 17 14:01:07 backup01        <HP Ultrium LTO 2>
> >
> > Aug 17 14:01:07 backup01 scsi: [ID 799468 kern.info] st60 at fp0: name
> > w50060b00002047f0,0, bus address 55
> >
> > Aug 17 14:01:07 backup01 genunix: [ID 936769 kern.info] st60 is
> > /pci@1d,700000/SUNW,qlc@2/fp@0,0/st@w50060b00002047f0,0
> >
> > Aug 17 14:01:07 backup01 genunix: [ID 408114 kern.info]
> > /pci@1d,700000/SUNW,qlc@2/fp@0,0/st@w50060b00002047f0,0 (st60) online
> >
> > Aug 17 14:01:07 backup01 scsi: [ID 365881 kern.info]
> > /pci@1d,700000/SUNW,qlc@2,1/fp@0,0/st@w50060b000020905c,0 (st61):
> >
> > Aug 17 14:01:07 backup01        <HP Ultrium LTO 2>
> >
> > Aug 17 14:01:07 backup01 scsi: [ID 799468 kern.info] st61 at fp1: name
> > w50060b000020905c,0, bus address 55
> >
> > Aug 17 14:01:07 backup01 genunix: [ID 936769 kern.info] st61 is
> > /pci@1d,700000/SUNW,qlc@2,1/fp@0,0/st@w50060b000020905c,0
> >
> > Aug 17 14:01:07 backup01 genunix: [ID 408114 kern.info]
> > /pci@1d,700000/SUNW,qlc@2,1/fp@0,0/st@w50060b000020905c,0 (st61) online
> >
> > Aug 17 14:01:07 backup01 scsi: [ID 365881 kern.info]
> > /pci@1e,600000/SUNW,qlc@4/fp@0,0/st@w50060b0000213e20,0 (st62):
> >
> > Aug 17 14:01:07 backup01        <HP Ultrium LTO 2>
> >
> > Aug 17 14:01:07 backup01 scsi: [ID 799468 kern.info] st62 at fp2: name
> > w50060b0000213e20,0, bus address 55
> >
> > Aug 17 14:01:07 backup01 genunix: [ID 936769 kern.info] st62 is
> > /pci@1e,600000/SUNW,qlc@4/fp@0,0/st@w50060b0000213e20,0
> >
> > Aug 17 14:01:07 backup01 genunix: [ID 408114 kern.info]
> > /pci@1e,600000/SUNW,qlc@4/fp@0,0/st@w50060b0000213e20,0 (st62) online
> >
> > Aug 17 14:01:07 backup01 scsi: [ID 365881 kern.info]
> > /pci@1e,600000/SUNW,qlc@4,1/fp@0,0/st@w50060b0000209064,0 (st63):
> >
> > Aug 17 14:01:07 backup01        <HP Ultrium LTO 2>
> >
> > Aug 17 14:01:07 backup01 scsi: [ID 799468 kern.info] st63 at fp3: name
> > w50060b0000209064,0, bus address 55
> >
> > Aug 17 14:01:07 backup01 genunix: [ID 936769 kern.info] st63 is
> > /pci@1e,600000/SUNW,qlc@4,1/fp@0,0/st@w50060b0000209064,0
> >
> > Aug 17 14:01:07 backup01 genunix: [ID 408114 kern.info]
> > /pci@1e,600000/SUNW,qlc@4,1/fp@0,0/st@w50060b0000209064,0 (st63) online
> >
> > =20
> >
> > =20
> >
> > =20
> >
> > Could it be possible my binding is incorrect for the QLogic HBAs?
> >
> > =20
> >
> > The problem is, with the sgscan utility, it does not find the drives on
> > st60, st61, st62, st63.
> >
> > =20
> >
> > I ran the sg.install command and re-created the
> > /kernel/driver/{st.conf,sg.conf} etc files but every time I run sgscan
> > it does not detect the drives.
> >
> > =20
> >
> > Has anyone run into a similar problem or issue before?
> >
> > =20
> >
> > In the meantime, I am doing further research to determine the root cause
> > of the problem, I have put the 1063's and 6410 back in the server and
> > did a reboot reconfigure and all devices appear without a problem.
> > There is something to do with the sg.install, the
> > /kernel/drv/{sg.conf,st.conf} files that I have not quite figured out
> > yet.
> >
> > =20
> >
> > My goal is to have it only probe for the devices that exist.
> >
> > I have attached all of the configuration files to this e-mail that
> > concern the tape and scsi information from /kernel/drv.
> >
> > In the end, it is probably something trivial, but at this time I cannot
> > seem to spot it.
> >
> > =20
> >
> > Qlc/qla2300 - (this config works and it sees the drives just fine, BUT I
> > cannot see them with sgscan).
> >
> > Yes I have done the sg.install commands but did not have any luck.
> >
> > Any help would be greatly appreciated.
> >
> > =20
> >
> > =20
> >
> > Thanks,
> >
> >
> > Justin.
> >
> >
>
> --kathy
>
> ===============================================================================
> Kathryn Hemness                        kfhemness AT ucdavis DOT edu
> System Administrator                   phone: 530.752.6547
> Campus Data Center & Client Services   fax:   530.752.9154
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
>

--kathy
 ===============================================================================
 Kathryn Hemness                        kfhemness AT ucdavis DOT edu
 System Administrator                   phone: 530.752.6547
 Campus Data Center & Client Services   fax:   530.752.9154