George,
Thank you for this information, it will be of great use in the future, but
unfortunately we are using a FCAW card, and the card driver is installed.
We do have Storage Tec coming back in today to check out the hardware,
hopefully they will find some thing wrong.
Regards,
Geoff Pusey
Tivoli Advisory Consultant
Tivoli Systems.
Office : +44 (0)1753 896896
Mobile : +44 (0) 780 8203704
Email : geoff.pusey AT tivoli DOT com
George Lesho <glesho AT AFCE DOT COM>@VM.MARIST.EDU> on 04/18/2001 10:33:13 PM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Problem configuring a Library
Since I have no way of knowing what you have done... here is a step by step
from
the beginning. I don't know why you are using a FC switch either...
* Copy driver file to a temp dir and uncompress...
* pkgadd -d <driver filename>
follow prompts to install
* READ the driver README file!
* go back and READ it again
* remove the Sun IFP driver and you may need to remove/reinstall your HBA's
device driver with the vendor & device ID #s
rem_drv ifp
(((follow README instructions for removing/reinstalling your HBA driver
it
may not be necessary)))
* You need to select a Hard AL_PA on your bridge. Since I don't know what
type
bridge or HBA is being used, the HBA will
read top to bottom or bottom to top but they usually read top down so
choose
E8 initially
* since your drives are type=scsi is to edit your /kernel/drv/st.conf file
to
ensure that you have support for all the tape
devices. It should look like:
tape-config-list=
"QUANTUM DLT7000", "QUANTUM DLT7000", "DLT7k-data";
DLT7k=data = 1,0x38,0,0x3D639,4,0x82,0x83,0x84,0x85,3;
name="st" class="scsi" ###this lun will provide support for your robot,
if
any
target=0 lun=0;
name="st" class="scsi"
target=1 lun=0;
name="st" class="scsi"
target=1 lun=1;
name="st" class="scsi"
target=1 lun=2;
(((((this will give you device support for 3 drives))))
* By selecting AL_PA E8, this will put your on bus1 and your robot will be
target 1 lun 0 on your bridge and your drives will
be target 1 luns 1-3 respectively. You have the ability to change the
target/lun setting for the robot (if you have one) and
for your DLT drives. Change them to the previously mentioned SCSI
addresses:
Robot Target 1 lun 0
drive 1 1 1
2 1 2
3 1 3
* You can delete the entries in /dev/rmt if you wish.
* type touch /reconfigure
* reboot -- -r (((the reboot will rebuild your devices in /dev/rmt based
on
the support you built into the tape-config-list.
* you will see the HBA show up in the banner and in /var/adm/messages. If
you
have a syntax error in st.conf, it will be
reflected there as well
Another way to this is to remove the special character files in /drv/rmt
and:
drvconfig -i <driver name>
devlinks
tapes
(((then look into /dev/rmt to ensure that the special character files were
created.
George Lesho
Storage / System Admin
AFC Enterprises
Geoff Pusey <Geoff_Pusey AT TIVOLI DOT COM> on 04/18/2001 03:38:18 PM
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: George Lesho/Partners/AFC)
Fax to:
Subject: Problem configuring a Library
Hi all,
I hope there is some one out there which can shed some light on this
problem. I have a SUN server where the TSM code is loaded (Version 3.7.4)
which has a fiber channel card which is in turn attached to a Fiber switch
(StorageTec 4116), of which a fiber to SCSI bridge is connected and then
the STKL700 library is connected to the Bridge.
____________ _____________________
__________________ ______________
| Sun system |___________| Fiber Switch |____|
Bridge |____| Library | 3 X DLT7000
Drives 1 X autochanger
|___________| |____________________|
|_________________| |_____________|
These are the entries I have put in the /usr/kernel/drv/mt.conf file
name="mt" class="scsi" class_prop="fcaw"
target=0 lun=0;
name="mt" class="scsi" class_prop="fcaw"
target=0 lun=1;
name="mt" class="scsi" class_prop="fcaw"
target=0 lun=2;
When I do the /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/mt I
get an error unable to attach to drive and there are no *mt rmt devises
created, and in the case of the lb driver it finds a CD rom drive which is
on the first SCSI inside the SUN system and not the SCSI card which is on
the other side of the Fiber.
How do I get it to look on the other side of the Fiber?
Regards,
Geoff Pusey
Tivoli Advisory Consultant
Tivoli Systems.
Office : +44 (0)1753 896896
Mobile : +44 (0) 780 8203704
Email : geoff.pusey AT tivoli DOT com
|
