SUMMARY: ADIC VLS DLT 400 Tape Media Changer not visible on Tru64 5.0A

From: <hofmannt_at_post.ch>
Date: Tue, 03 Oct 2000 15:47:37 +0200

Thanks to all who responded.

I could not find the solution to create the device file for the changer
manually.
Rescan scsi buses didn't work.

Because I use the changer only temporary (we will connect to a centralized
backup)
I didn't try additional utilities.

>From vendors support I received the information (after a few weeks) that
adic
don't support Tru64 Unix. In other words: no help.

My solution is to put the changer in serial mode which loads the next tape
after
I unload the tape with the "mt unload" command.

Cheers,
Thomas Hofmann

Original responses follow

-----Original Message-----
Hello Admins

I have a Tape Media Changer "ADIC VLS DLT 400" attached to a DS20 with Tru64
5.0A.

On the console I see

ADIC VLS DLT 0305 #( Changer )
Quantum DLT4000 D069 #( Tape Drive )

>From the Unix I see only the tape.

After reading in the manuals I know that the changer driver is in the
kernel:

# sysconfig -s cam_changer
cam_changer: loaded and configured

What am I doing wrong?

Thanks for any help.

-----Received Answers-------------

Davis, Alan [Davis_at_tessco.com]

I have been trying to get a ddr.dbase entry for the ADIC loaders for several
months. I'm still hopefull that ADIC will come thru with one, it's just a
matter of finding the right person there that has the information.

You can use it in "sequential mode", but the mcutil or robot commands won't
be able to access slots randomly. I haven't been able to get Networker to
see the loader either, even though they list it as a supported device on
Tru64.

If you get a ddr.dbase entry before I do, please post it to the list.

Thanks,

Alan Davis
davis_at_tessco.com

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

Roetman, Paul [PRoetman_at_CSXLines.com]

Have a look at the Robot commands

but first, they must be loaded....

ROBOTBASE140 installed Media Robot Utility V1.4
ROBOTCDE140 installed MRU CDE Graphic User Interface V1.4
ROBOTDOC140 installed MRU Online Documentation V1.4
ROBOTGUI140 installed MRU Motif Graphic User Interface V1.4
ROBOTHTML140 installed MRU HTML Documentation V1.4
ROBOTMAN140 installed MRU Manual Pages V1.4
ROBOTPGMR140 installed Media Robot Driver Library V1.4

These commands will give you access to control the cam. It works for our
system here:

scu> show edt

CAM Equipment Device Table (EDT) Information:

    Bus/Target/Lun Device Type ANSI Vendor ID Product ID Revision
N/W
    -------------- ----------- ------ --------- ---------------- --------

---
     1    5    0   Sequential  SCSI-2 DEC       TZ875    (C) DEC   9514    N
     1    5    1   Changer     SCSI-2 DEC       TZ Media Changer   9514    N
Cheers
Paul
----------------------------------
alan_at_nabeth.cxo.dec.com
	Please expand on "From the Unix I see only the tape."  V5.0A
	does include an updated media changer driver from the old
	CLC kit.  I think it also includes mcutil, so you can have
	some control over the library if you can figure out the
	command.  If the media changer is well behaved, the driver
	should find it and whatever part of the boot that creates
	special files will create the appropriate special device.
	If not, then look at the device and hardware manager commands
	to see if you can force them to rescan the particular bus
	and recreate the necessary files.  If those don't work,
	then maybe the media changer is not as well behaved as you
	might hope.
----------------------------------
Dr. Tom Blinn, 603-884-0646 [tpb_at_doctor.zk3.dec.com]
I asked my colleague who is an expert in these matters whether he
had any insight into your problem, and he wrote back:
------- Forwarded Message
To: "Dr. Tom Blinn, 603-884-0646" <tpb>
Subject: Re: Any suggestions for this poor user?
We've seen similar things several times now.
Either your changer or your tape are not generating a unique
serial number (or IEEE identifier) (INQUIRY pages 0x80 and 0x83)which
we use in 5.x to generate a WWID.
This is necessary for us to recognize the device via multiple paths.
See if you can get a firmware upgrade from the mfr.
Gary
http://www.scsifaq.org/ -- A waist is a terrible thing to mind!
------- End of Forwarded Message
I can't tell whether he passed a copy of the answer along to you, so
I am forwarding it (above).  If this is a duplicate, my thanks go to
him for cc-ing me as well.
As an alternative, I believe we have a way using the "hwmgr" or one
of the other utilities to generate a WWID for the device, but I'm not
expert in this area and you might need to go reading the man pages and
manuals if you can't get firmware that exports a WWID directly.
Tom
 
 Dr. Thomas P. Blinn + UNIX Software Group + Compaq Computer Corporation
  110 Spit Brook Road, MS ZKO3-2/W17   Nashua, New Hampshire 03062-2698
   Technology Partnership Engineering           Phone:  (603) 884-0646
    Internet: tpb_at_zk3.dec.com            Compaq's Easynet: alpha::tpb
     ACM Member: tpblinn_at_acm.org         PC_at_Home: tom_at_felines.mv.net
  Worry kills more people than work because more people worry than work.
      Keep your stick on the ice.        -- Steve Smith ("Red Green")
     My favorite palindrome is: Satan, oscillate my metallic sonatas.
                                -- Phil Agre, pagre_at_alpha.oac.ucla.edu
     Yesterday it worked / Today it is not working / UNIX is like that 
			-- apologies to Margaret Segall 
  Opinions expressed herein are my own, and do not necessarily represent
  those of my employer or anyone else, living or dead, real or imagined.
 

Received on Tue Oct 03 2000 - 13:47:07 NZDT