I don't think I would ever define name of jukebox with space in it.  Actually, I thought that was not possible :-D

Anyway, most likely address of jukebox is not the same.  Do nsrjb -V and see what is the control port.

Then do inquire, inquire -cl and inquire -s and see what address jukebox is now on.  If lucky, all you have to do is to change control port in NW jukebox definition.

Please try to reboot the NW server and make sure nsrlcpd process is up and running.

Good Morning Hrvoje Crvelin,

Thanks for replying. below are the steps I have done so far.

1. I did try inquire and changer command to see the juke box details but came up with nothing.

2. when I got the message jukebox not available I had a look at the server to find out what are the devices attached to it through dmesg and found nothing.

we should be able to see 2 devices attached to the server but found nothing.

so we have requested the datacentre guy to have a look at the jukebox and before that we had shutdown the server and the data centre guy has powered off the library and removed all power and network cable including fibre channel and connected them back after a while powered them up.

He had a look at network setting of the library

Mode: Random

Auto Clean : Enabled

Autoload : N/A

Loop : N/A

Active Slots : 23

DHCP : off

and some IP addresses.

Now the library is scanning and moving the cartridges and these is a sort of error message saying 'Drive log out FB 00'

but still we cant see this from server side.

Any inputs?

Thanks,

Phani

Good Morning Raja,

We tried rebooting the server as well but no luck. I can see nsrlcpd is up and running before and after the reboot.

Any inputs will be great.

Thanks,

Phani

Since you started with the conversation with the fact that the server was rebooted, it might be that the scsi address for the library has changed. Please provide the output of the following commands:

inquire

printf " . type: nsr jukebox\nprint\n" | nsradmin -i-

If you can't see it from server side (OS), then this won't be resolved before that point has been addressed.  NW uses system calls to see the library and if that is not there, it won't work.

Good Morning Crazyrov,

I did run that command and haven't got anything. First need to check why we arent able to see the jukebox from OS side?

Thanks,

P

I also think that the SCSI address might have changed.

  - First check whether the OS sees the 'new' device.

  - Then INQUIRE will help to verify the current address.

  - Finally adjust the address in the jukebox configuration.

This should do the job.

phani6039, yes if inquire is not able to see the devices then it must be something on the OS or the hardware side that is the poblem. What OS do you have your NetWorker server hosted on.

Thanks for the reply bingo

Unfortunately still OS cant see the new devices. Not sure if am missing any thing here.

I had a look at the networker administrator gui interface which is hosted on the server and found the attached stuff. In  screenshot below it is using control port scsidev@1.0.1  under library section which is not at all visible on the OS level when I had a look with with inquire -sl and lsscsi. Also library status is disabled.

The datacentre guy had a look at the library and he had a look at the settings and performed reinventory of all tapes and confirmed everything ok from his library side.

Not sure where to start now as I am unable to see the scsi device that is configured under library.

Thanks,

Phani