Check Mailslots

Yes... it is called sjirdtag.  You use it as sjirdtag b.t.l (bus.target.lun is control address of your lib which you can see via inquire command or from control port data for jukebox in NetWorker).

You could also use the following command to get the output as summary

sjirdp

Hi,

thanks for your replies but both commands didn't work.

I check the nsrjb -Vv command to geht the devname of a library

Configuration information for jukebox HP@2.0.1:

        model: Standard SCSI Jukebox

        control port: scsidev@2.0.1

        bar code reader: Yes

        jukebox features: volume_tags elements_status read_elem_unload_fail barcode no_trnsport_source_dest

        number drives: 2

        devices: /dev/rmt/3cbn rd=filer01:nrst6a (NDMP) /dev/rmt/4cbn rd=filer01:nrst7a (NDMP)

        physical slots: 1-45

        cleaning slots: 45-45

        available slots: 1-44

        operation timeout: 1800 seconds

So i tried:

sjirdtag scscidev@2.0.1
scscidev@2.0.1: No such file or directory"

sjirdtag HP@2.0.1

HP@2.0.1: No such file or directory

sjirdtag 2.0.1

2.0.1: No such device

sjirdp HP@2.0.1

HP@2.0.1: No such file or directory

sjirdp scscidev@2.0.1

scscidev@2.0.1: No such file or directory

sjirdp 2.0.1

2.0.1: No such device

Inquire does not show the libraries at all. It only shows the 4 Disks of the server, the CDROM and the 4 tape drives (2 in each library)

ISt there something missing ? Any ideas ?

As H already mentioned sometime the when the nsrlcpd is using the library the library cannot be accessed by any other daemon or binary. You might have to try disabling the library in NetWorker and then try the command again. The output should look something like below.

$ sudo sjirdp 130.0.1

130.0.1 has   8 DATA TRANSPORT Element(s) starting at address 1

130.0.1 has   2 MEDIA TRANSPORT Element(s) starting at address 1

130.0.1 has 580 STORAGE Element(s) starting at address 1

130.0.1 has  16 IMPORT/EXPORT Element(s) starting at address 1

sjirdtag 2.0.1 should work.  I believe in some recent versions, one of nsr daemons might block access, but then you get device busy.  You can disable lib in NW for test and see if sjirdtag 2.0.1 works then.  You should also see lib in inquire.  Note that command must be executed on box controlling robotics of course and not anywhere else (like remote storage node).  Meanwhile, I assume you can also use library GUI to see IE ports.

If your robotic is also on filer, then sjirdtag can't be used of course so you will have to rely on library GUI (most libraries have that).