I don't think the IFP driver is installed:
tsm22001# modinfo | grep -i ifp
tsm22001#
But thanks for the answer. I've got the st.conf sorted - I had done that
before on a different box but it was directly-attached FC-AL rather than
fabric. It's more the question of what to put in mt.conf and when to do
"add_drv mt".
And thanks to Suad and Richard for your answers too. I now feel a lot
better equipped to work with the storage guys. I always get neverous when
someone says "just give me the root password, I'll configure it" -
especially when I'm the one who has to produce the documentation.
-----Original Message-----
From: George Lesho [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 02, 2001 5:19 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM, SAN, ACSLS and Solaris
To configure the qlogic hba, did you first remove the Sun IFP driver? You
probably need to do this and reinstall the qlogic driver with the vendors
id#'s
* rem_drv ifp
* rem_drv qla2200
* add_drv -c scsi ' "<<<vendor's devide id #>>>" ' qla2200
* Then you will edit your st.conf file to make sure support for the tape
drives
you are using is selected by uncommenting
references to them
This will look like:
tape-config-list=
"QUANTUM DLT7000", "Quantum DLT7000", "DLT7K-data";
DLT7k-data = 1,0x38,0,0x1D639,4,0x82,0x83,0x84,0x85,2;
there is some sort of readme file to explain how to link the wwn with the
devices as I recall.. I haven't seen a swith or FC for a couple years... If
I
recall correctly this will be done in the qla2200.conf file.
* touch /reconfigure
* reboot - - -r
The system reads the driver config file as well as the st.conf and builds
NEW
device files in /dev/rmt... in fact, you can remove the old ones first if
you
like, they won't work if the stuff isn't configured right anyway. You will
see
references to the new HBA your banner and /var/adm/messages once it is
installed
right. If you have syntax errors in the st.conf, these will show up in the
banner and /var/adm/messages. Does qlogic or the O/S (sorry I am in an all
AIX
env now) give you a utility called drvconfig? If so, I think you can also
run
the thing to build your special dev files...
drvconfig -i qla2200
devlinks
tapes
---then look into /dev/rmt to see if the special character files necessary
for
dev support were created....
George Lesho
Storage/System Admin
AFC Enterprises
drvconfig?
"Walker, Lesley R" <[EMAIL PROTECTED]> on 02/28/2001 09:24:50 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: George Lesho/Partners/AFC)
Fax to:
Subject: Re: TSM, SAN, ACSLS and Solaris
Hi Ron, thanks again for the answer.
Sorry to be asking so many questions, I just don't know much about
fibre-channel and even less about switched fibre-channel.
So, is a world wide name a sort of alias that creates a tunnel through the
switch in this case? Could I just pick, say SCSI-ID 2 and put in a line
that says
hba1-SCSI-target-id-2-fibre-channel-name="something"
and then as long as "something" points to the right thing it will work? Or
does it have to be the right SCSI-ID?
One thing that's holding me back is not having any doco for the Qlogic card
(it was "borrowed" from another project) so thanks for pointing me at the
qla2200.conf file.
Another general Solaris question, is it safe to do "boot -r" before running
the add_drv commands? I was told very early on to never do boot -r at all,
but I suspect this advice may have been a bit bogus.
We have JNI cards in the box as well (for connecting to EMC) so it gets
rather confusing! (The box is an E4500 if that matters)
-----Original Message-----
From: Ron Pavan [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 01, 2001 12:36 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM, SAN, ACSLS and Solaris
I believe what you are looking for is placed in a conf file. example: We
have a sun e3500 running with QLogic HBA's. We define a target-id to a
world wide name on a fiber switch (can can also define a target to a port
number on the switch but then you are limited to that port and if the port
goes bad you cannot switch ports without a reboot). This config files is
\kernel\drv\qla2200.conf. When you reboot/reconfigure the st.conf should
scan for targets that can now be found because the HBA is defining them.
-----Original Message-----
From: Walker, Lesley R [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 28, 2001 2:34 PM
To: [EMAIL PROTECTED]
Subject: Re: TSM, SAN, ACSLS and Solaris
Thanks for the answer, and thanks to the others who answered too.
The part that I'm trying to figure out now is how to install the drivers.
With Solaris, you have to edit a file that contains definitions of the
SCSI-IDs of the tape drive. How can that work if the tape drives are
assigned via a switch? Do you set up some kind of permanent virtual circuit
so that you always get the same drives?
Please excuse my ignorance - I have no access to the SAN switch doco, as it
is being set up by people in another team in a different city.
The latest information I have on the switch is that it is either Inrange
FC9000-16 or Brocade Silkwork 2800.
