Difficulty attaching tape library disks to Networker 9.0

Question

We currently are using networker 9.0.0.2 to attach an HP MSL4048 tape library.  We have the drivers installed on 2012 R2,  We followed the admin guide for adding the new library, it detected two tapes (//./Tape0 //./Tape1) yet when we try to access them or mount them it fails. Per the support tech I spoke with this morning: ' We should see the autochanger like scsidev@2.8.0:STK L80             0104|Autochanger (Jukebox), /dev/sg11 So this is an OS level issue. ' Yet the device path above looks to be unix based /dev not windows.  When a jbverify command is run it times out trying to communicate with the tapes after 10 tries. From the NMC console the error seen: \.\Tape0 read open error: command completeled successfully (drive status is There is not a tape in the drive) There was only a single driver available for all windows OS versions of the Tape Library so I'm a bit confused.  Any guidance other than linking the 9.0x admin guide would be welcome. Thanks,

Karthik_N1 · Accepted Answer

Please confirm if the library is attached to remote storage node or server itself?

Try to mount the volume through sjimm command

Syntax: sjimm scsidev@b.t.l slot 1 drive 1

After that check the status of the drive

Command: mt -f scsidev@b.t.l status

Generally read open error is encountered when there is drive firmware issue, also make sure drive firmware is appropriate.

Thanks,

Karthik N

bingo.1 · Answer

First of all - may I suggest that you install the latest NW 9 version (9.0.1.1) to avoid all other potential problems.

The driver situation is o.k.

- device drivers are delivered by the drive manufacturer

- library drivers are not needed - the NW storage node software contains all necessary code.

It really looks as if the autochanger is attached to a UNIX/Linux node. Although it is possible that the drives are connected to the NW server and the library is connected to another host (storage node), it is not a good idea to do this unless it is absolute necessary.

The effect you see might occur if the library control is based on FC and the paths are not properly configured. You need to correct that before you delete and reconfigure the library. Use the NW inquire command to verify that.

dpeoples83 · Answer

Thanks for the assistance.  Power cycling the tape library after verifying all the drivers appears to have solved the issue.

NetWorker

Was this post helpful?