Here's what I have on the Solaris 9 server:
# lusbinfo
# busses: 3
Bus #0 is 'glm0', dma_max=16777215, initiator ID=7, ntargets=16, nluns=7
Bus #1 is 'pci1077,20', dma_max=16777216, initiator ID=255,
ntargets=126, nluns=32
Bus #2 is 'pci1077,21', dma_max=16777216, initiator ID=255,
ntargets=126, nluns=32
(This is a dual-port QLA2200 card, so that makes sense.)
And here's my known-scsi-devices line:
known-scsi-adapters="esp:8-7 SUNW,esp:8-7 isp:16-7 SUNW,isp:16-7
QLGC,isp:16-7 fas:16-7 SUNW,fas:16-7 glm:16-7 SUNW,glm:16-7
pci1000,f:16-7 ifp:126-126 SUNW,ifp:126-126 PTIX,isptwo:126-126
pci1077,2100:126-126 pci1077,1:126-126 pci9004,8478:16-7
pci10df,f700:126-32C pci10df,f800:126-32C pci10df,f900:126-32C
fca:126-32C fcaw:126-32C pci1242,4643:126-32C pci1077,2200:126-32
JNI,FCE:126-32C fce:126-32C JNI,FCR:126-32C fcr:126-32C fp:126-32
pci1077,2:126-32 pci1077,9:126-32 pci10cf,105c:126-32C
pci10cf,1178:126-32C pci10cf,12c3:126-32C fjulsa:16-7 ";
name="lus" class="scsi" target=0 lun=0;
You can see that my adapter is listed there.
Since the problem that I was having (on Solaris 9) was multiple
references to the robotic device, I edited the known-scsi-adapters line
leaving just the references to the scsi adapters that I'm using:
known-scsi-adapters="glm:16-7 pci1077,2:126-32C";
name="lus" class="scsi" target=0 lun=0;
I rebooted and all appears well.
Now, on to the Solaris 10 server. The lus stuff appears to not apply,
but I'm not sure what to do next. Inquire shows nothing but the disk
drives on the box.
---
W. Curtis Preston
Author of O'Reilly's Backup & Recovery and Using SANs and NAS
VP Data Protection
GlassHouse Technologies
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Yaron Zabary
Sent: Tuesday, May 29, 2007 12:19 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] inqure & jbconfig not working in Solaris 9/10
If the HBA's PCI inquiry string is not in lus.conf, inquire will not
show the devices. I had a similar issue with an Emulex 9802 HBA on a
Sparc 280R with Solaris 9. What you need to do is (that's of course
after the proper installation of HBA drivers, zoning or any other OS
related issues):
Run lusbinfo and find out the inquiry string of your HBA (my two
Emulex shows up as pci10df,f9800 and pci10df,f9801):
# lusbinfo
# busses: 7
Bus #0 is 'pci1000,f0', dma_max=16777215, initiator ID=7, ntargets=16,
nluns=7
Bus #1 is 'pci1000,f1', dma_max=16777215, initiator ID=7, ntargets=16,
nluns=7
Bus #2 is 'pci10df,f9800', dma_max=-1, initiator ID=255, ntargets=32,
nluns=8, lus cloning enabled
Bus #3 is 'pci1077,10162', dma_max=16777215, initiator ID=7,
ntargets=16, nluns=7
Bus #4 is 'pci1077,10163', dma_max=16777215, initiator ID=7,
ntargets=16, nluns=7
Bus #5 is 'fp0', dma_max=16777216, initiator ID=127, ntargets=126,
nluns=7
Bus #6 is 'pci10df,f9801', dma_max=-1, initiator ID=255, ntargets=32,
nluns=8, lus cloning enabled
You need to edit /usr/kernel/drv/lus.conf and add this to the end of
the known-scsi-adapters strings pci10df,f980:32-8C . Notice that you
need to omit the last digit. The 32 is number of targets on the bus and
8 is max luns per targets. C stands for cloning (whatever that means,
this was suggested for the Emulex 9000 cards, so I figured it will be
suitable here as well). Anyhow, all these are documented in the file
itself.
Curtis Preston wrote:
> I'm trying to configure NetWorker on three test machines where we JUST
> previously had NBU installed and running fine. They can all see a
Fibre
> Channel attached VTL that's pretending to be ATL P1000 with 8 9840C
> drives in it. NBU configured this and used it NO PROBLEM.
>
>
>
> We UNinstalled NBU and made sure the sg driver was gone. Now we're
> trying to install NW, and it's giving us fits. It configures just
FINE
> on the RedHat Enterprise Linux server, but it won't configure on the
> Solaris 9 or 10 box.
>
>
>
> On both systems, I can see the proper number of devices in
> /dev/scsi/changer and /dev/scsi/sequential, but...
>
>
>
> On Solaris 9, it lists 64 different instances of the robot device, and
> on Solaris 10 it lists NONE.
>
>
>
> I even tried manually configuring them using the device I can see in
the
> /dev/scsi/changer, and it says it sees no robot there. What's up with
> THAT?
>
>
>
> HELP!!!
>
>
>
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
