Start a Conversation

Unsolved

S

7 Posts

527

December 6th, 2022 22:00

Autochanger(Jukebox) not getting listed on storage node

We found error with our clone to tape backup.

after checking we found that Autocharger(Jukebox) not getting listed on storage node OS.

As below:

C:\Users\Administrator>inquire -lc

-l flag found: searching all LUNs, which may take over 10 minutes per adapter
        for some fibre channel adapters.  Please be patient.

scsidev@15.239.0:DELL    PERC H750 Adp   5.16|Disk, \\.\PhysicalDrive0
                                           S/N: 0075dfe13ab7e0662900aa1a1080e04e
                                           WWNN=6F4EE080101AAA002966E0B73AE1DF75
scsidev@15.254.0:  RAID   DummyDevice    0001|Unknown Device Type,
scsidev@16.3.0:IBM     ULT3580-HH8     N4Q1|Tape, \\.\Tape3
                                           S/N: 11768EB083
                                           ATNN=IBM     ULT3580-HH8     11768EB083
                                           WWNN=5000E111768EB083
                                           WWPN=5000E111768EB084
                                           WW2N=5000E111768EB083
                                           PORT=00000001
                                           Can Encrypt & Decrypt
scsidev@16.7.0: Unknown error
scsidev@16.7.1: Unknown error
scsidev@21.3.0:IBM     ULT3580-HH8     P381|Tape, \\.\Tape1
                                           S/N: 11768EB079
                                           ATNN=IBM     ULT3580-HH8     11768EB079
                                           WWNN=5000E111768EB079
                                           WWPN=5000E111768EB07A
                                           WW2N=5000E111768EB079
                                           PORT=00000001
                                           Can Encrypt & Decrypt
scsidev@21.7.0:IBM     ULT3580-HH8     P381|Tape, \\.\Tape0
                                           S/N: 11768EB065
                                           ATNN=IBM     ULT3580-HH8     11768EB065
                                           WWNN=5000E111768EB065
                                           WWPN=5000E111768EB066
                                           WW2N=5000E111768EB065
                                           PORT=00000001
                                           Can Encrypt & Decrypt
1 Disk, 3 Tape, 1 Unknown Device Type, Total: 5

Anyone can give some input on this?

2.4K Posts

December 7th, 2022 02:00

Your configuration looks somehow weird because there is also the gap created by the missing \\.\Tape2 .

I guess that there is a FC controller/connection problem. 

May I suggest that you first check the availability with HP Tape Test Utilies and correct the problem before you rerun INQUIRE.

 

December 19th, 2022 10:00

The configuration within NW should tell you which scsi id was configured to access the robotics. As I also see two devices mentioned (16.7.0 and 16.7.1) that state Unknown Error, that would be worthwhile knowing from the tapelibrary end if and what might be the matter with the library if anything?

When we still had tapelibraries, I also heavily used the sji tools on the NW SN's controlling the robotics, like sjirdtag. But as the inquire output doesn't seem to show the robotics, what was or is or should be the scsi id for that? Also in relation to the two Unknown Error devices.

So if the robotics arm is one of those two affected scsi id's, then you'd know why the library no longer can be managed and why you might be missing Tape2?

Also those device names don't seem to suggest persistent naming? Which is the -p option of inquire. On Windows I'd then expect names like Tape4801144 instead of Tape1. So what kinda device names do you have configured within NW?

–p Tells inquire to display persistent device names for devices on platforms where
persistent names are supported. If persistent names do not exist for any particular
device then the normal device name will be shown. Currently only
linux has such support. Specifying –p on a platform that does not have
NetWorker-recognized persistent names will have no effect.

No Events found!

Top