can't access DLT tape via fiber

[Steve Coates]

I have tape drives connected via fiber channel.

I have attached an ioscan of the tape devices.

The error I get is

/dev/rmt/0m: No such device or address

[Helen French]

I assume you are not entering "Om" instead of "0m", it's normally a typo.

What would be the output of lssf command:

# lssf /dev/rmt/0m

What about other devices - 1m or 2m? Are they working? What command are you testing?

[Steve Coates]

stape card instance 21 SCSI target 0 SCSI LUN 3 at&t best density available at address 0/0/8/0/0.1.7.255.0.0.3 /dev/
rmt/0m

I was just using mt -f /dev/rmt/0m rewind

All of the devices give the same error

[Helen French]

Again, this can be becuase of the configuration of your robotic arm. What type of device is that? did you configure it properly?

# ioscan -fnC autoch
# ioscan -fn

Check and see if your robot arm device is configure properly and is CLAIMED. If not, configure that first. Also, some commands and applications (Omniback, Legato, veritas etc) are specific to the driver you use for tape devices. Load the proper device drivers - stape, tape2, spt etc.

[Steve Coates]

I am not tryin to control the robot just trying to talk to the tape drives. I can access them from other machines that are connected to the fiber network but not this one.

[Helen French]

I understand. But in order to talk to the drives, you need to talk to the robot arm first (I assume you are using a library ..rt?). For that, you need to configure the robot arm. Find out the device driver for the robot arm from other servers and then configure the same here.

[Steve Coates]

The robot arm is not configured on any of the machines at this time, have not got to that yet.

The tape was placed in the drive using the jukebox (HP ESL9000) control panel.

[Richard Pugh_2]

You will not be able to do a rewind unless there is a tape in the drive and has been forwarded to at least 1 block.

Does the drive(s) have a tape in them?

Do you have the proper drivers installed?

[Steve Coates]

In case anyone would want to know what the outcome of this is.

It ends up one of the fiber to SCSI routers was having a problem. It was replaced and now everything works.

Stev