Connecting DLT7000 to L 2000

[Kevin Lamb_2]

Hi,

I am trying to connect a StorageTek 9714 tape library with 6 DLT7000's, I am using an L2000 running HP-UX11.00.

The SCSI card is a dual port LVD (LVD/SE) using 68pin VHVD to 68pin HVD cables, the server sees the old DLT4000's in the Old library which has SE SCSI inputs without a problem; however, when connecting to the new library it cannot see the DLT7000's.

I have tried to connect a single DLT7000 within the library to discount the library's own controller but the L Class still refuses to recognise this.

Anyone got any suggestions/clues.

Kev
"I'd rather be flying"

[Robert DJ]

Hi Kev,

Are all drivers installed for the DLT7000.

If No, Please install the Drivers for DLT7000.

If yes, The problem might persisting to the hardware card supporting to the Tape library.

Need a little more info about your setup and trial you've made

Regards,
Robert.

[Kevin Lamb_2]

Hi Robert,

I have installed all the tape drivers that were available (are there seperate ones for DLT7000?)

So far I have tried connecting a single DLT7000 within the library directly to the dual LVD/SE card, I have also changed the SCSI addresses on the DLT just in case, I have tried connecting directly to the library and terminating all but 2 DLT's but this still fails to recognise the tape devices.

Not sure what other info that you require, let me know and I will post it.

Thanks,
Kev
"I'd rather be flying"

[Mark Grant]

Is ioscan just completely ignoring the thing or does it have "NO_HW" ?

[Kevin Lamb_2]

Hi Mark,

Ioscan does not show anything at all connected to the SCSI.

Kev
"I'd rather be flying"

[Bernhard Mueller · Accepted solution]

Hi,

I don't think it will work because all the DLT7000 drives I know are HVD (HighVoltage Differentail) devices. Your card is LVD (LowVoltage Diff). You see the DLT400 because it is an SE device, to which mode the LVD card can revert (LVD/SE) but the DLT7000 is (most likley) NOT a single ended device

Regards,
Bernhard

P.S. I think there are converters which you *might* use, but I guess you are aiming at an officially supported configuration...

[DGH_2]

Hi,
please,can you post the output of ioscan.

DGH

[Kevin Lamb_2]

Bernhard,

Thanks, I think you might have hit the nail on the head, I was thinking along those lines but was unsure as the cables that we use are 68to68 VHVD-HVD and this is what prompted me to think it would work.

DGH
I cannot send an output of the ioscan as we did not record it as it happened and we had to back out of the plan and put the old library back in place with the DLT4000

Kev,
"I'd rather be flying"

[John Palmer]

We haven't got any DLT7000's connected to L class but all the DLT8000 drives are connected via Fast Wide Differential SCSI cards.

Example ioscan:-
ext_bus 4 0/2/0/0 c720 CLAIMED INTERFACE SCSI C875 Fast Wide Differential
tape 1 0/2/0/0.3.0 stape CLAIMED DEVICE QUANTUM DLT8000
/dev/rmt/1m /dev/rmt/c4t3d0BEST
/dev/rmt/1mb /dev/rmt/c4t3d0BESTb
/dev/rmt/1mn /dev/rmt/c4t3d0BESTn
/dev/rmt/1mnb /dev/rmt/c4t3d0BESTnb

Regards,
John

[Robert DJ]

Hi Kev,

Just try out this out, before that pls take backup of the Workstation for safety reasons.

If drivers are not getting matched. Take a backup of your kernel and system file which i've mentioned below.

1. Verify that the unit has a SCSI interface compatible with the SCSI controller that is installed.

2. Determine the availability of SCSI Ids. use ioscan -f

3. Each SCSI bus must have a unique SCSI Id. Find out whether the Id is matched to one assigned.

4. Check out to configure using the utility of the backup, and set the tape library to SCSI.

5. try going to build area - cd /stand/build.

6. Create a system file from the existing kernel.
/usr/lbin/sysadm/system_prep -s system

7. check if the stape driver is already configured into your system. the stape
driver used for the DLT drivers can checked by -

#grep stape system

8. If no "stape" line printed, add a line to the "SCSI drivers" area of the system file (/stand/build/system)

stape

9.check if sctl SCSI pass-through driver is already confgiured into your current
kernel.

#grep sctl system

10. If no "sctl" line printer, add a line to the "SCSI drivers" area of the system file (/stand/build/system)

sctl

A driver statement is needed since the system can't autoconfigure the SCSI
pass-through driver.

11. Append the driver lines to the system file

driver sctl

Note : = Complete hardware path of derised device from ioscan

e.g - driver 8/4.6.0 sctl


12. save the old system file

mv /stand/system /stand/system.old

13. Build a new kernel

/usr/sbin/mk_kernel

14. Verify the pass-through driver has been built into the new kernel.

what ./vmunix_test | grep scsi_ctl

15. Save the old kernel

mv /stand/vmunix /stand/vmunix.old

16. Move the new kernel to the current one :

mv ./vmunix_test /stand/vmunix

17. Boot the system

/usr/sbin/shutdown -r 0

18. Once restarted

verrify using "ioscan -f"

19. Determine the major number for the SCSI pass-through driver.

lsdev -d sctl

The O/p might be,

Character Block Driver Class
203 -1 sctl ctl


20. Create the special device file to access the scsi_ctl perpheral

/usr/sbin/mknod /dev/<> c

- name of the special device file

- character major number (from lsdev cmd)

- minor number in the format 0xIITL00

II - 2 digit card instance number of "ext_bus" entry

T - target SCSI ID number (SCSI ID)
L - Lun number (SCSI LUN)
00 - Reserved fields, must be zero

E.g : /usr/sbin/mknod /dev/rmt/lxb c 203 0x006000

21. Type "ioscan -fd sctl"

Check whether the driver is configured.

22. Complie the scsi i/o test program

cc /usr/contrib/src/scsi_io.c
-o /usr/contrib/bin/scsi_io

23. Run SCSI i/o test program

/usr/contrib/bin/scsi_io /dev/rmt/lxb

The display should some what similar to this,

OVERLANDLXB 032322-Oct-97

Let me know if you still persist with the problem.

Thanx & Regards,
Roby