This post is more than 5 years old
19 Posts
1
10899
February 12th, 2015 08:00
read open error: there was not a device file name passed in to CDI (drive status is )
I have a Networker v. 8.1.1.5 Build 306 with a Quantum Scalar i80 connected for Backups.
I changed the tapes and tried to Inventory and Label the Tapes to be functional for new Backups.
9 tapes were put in the Scalar but only 4 were Labeled the other 5 are unlabeled.
After Inventory all the tapes, I've tried to mount one by one and do the Label of the Tape, but it gives me the error: "read open error: there was not a device file name passed in to CDI (drive status is )".
I've checked the Networker console, made the Inquire but can't see this drives.
I have also, connected to this networker a VTL Service from DD and a Dell MSL6000.
This is the Inquire output:
--------------------------------------------------------------------------
DEVICE :VEND :PROD :REV :SER NUM :CAP(kb)
--------------------------------------------------------------------------
/dev/sda :DELL :PERC 6/i :1.11 : : 71041024
/dev/sdb :DGC :VRAID :0430 : : 104857600
/dev/sdc :DGC :VRAID :0430 : : 104857600
Occasionaly the Drive enters in Service Mode while is making the Inventory.
Anyone had this problem before ?
Any help will be welcomed.
Best regards,
FQ
ble1
2 Intern
•
14.3K Posts
0
February 13th, 2015 05:00
I'm not sure what CLI console it for you, but if they refer to the same thing they should not display two different things since they read same nsrdb resources. What you can do is:
a) make sure drives are not loaded
b) delete lib in NW
c) delete devices for this lib in NW
d) configure it again
e) check device paths
crazyrov
4 Operator
•
1.3K Posts
0
February 12th, 2015 08:00
This could be a device driver related issue as the inquire is not able see all the tape drives. What OS is your NetWorker server ? Also try the following command on each of those devices.
cdi_inq -f device_name
FQuintino
19 Posts
0
February 12th, 2015 09:00
Hello crazyrov,
Linux RedHat
Distributor ID: RedHatEnterpriseServer
Release: 6.1
Inquiring the device it says that drive is ready.
Inquiring Library
Standard Inquiry data:
Vendor: QUANTUM
Product: Scalar i40-i80
Rev: 150G
VPD pages supported:
Pages 00 80 83
Serial number page (80):
QUANTUMD1H0060819_LLA
Device ID page (83):
ATNN=QUANTUM D1H0060819_LLA
cdi_info.drivestat is:
status = 0, DRIVE_STATUS_READY
msg = The tape drive is ready for use
And the Scalar drives, it shows me 4 drives (but physically I only have 2):
scsi-3500308c38b8af000
scsi-3500308c38b8af000-nst
scsi-3500308c38b8af004
scsi-3500308c38b8af004-nst
And the Inquiries are these:
Standard Inquiry data:
Vendor: HP
Product: Ultrium 4-SCSI
Rev: V61Z
VPD pages supported:
Pages 00 80 83 85 86 87 88 b0 b1 b2 c0 c1 c2 c3 c4 c5
Serial number page (80):
C38B8AF004
Device ID page (83):
WWNN=500308C38B8AF004
WWPN=500308C38B8AF005
PORT=00000001
UNKN=00000000
WW2N=500308C38B8AF004
ATPN=HP Ultrium 4-SCSI C38B8AF004
Non-standard pages displayed only with -v parameter
cdi_info.drivestat is:
status = 0, DRIVE_STATUS_READY
msg = The tape drive is ready for use
[root@LPANWO01 by-id]# cdi_inq -f scsi-3500308c38b8af000
Standard Inquiry data:
Vendor: HP
Product: Ultrium 4-SCSI
Rev: V61Z
VPD pages supported:
Pages 00 80 83 85 86 87 88 b0 b1 b2 c0 c1 c2 c3 c4 c5
Serial number page (80):
C38B8AF000
Device ID page (83):
WWNN=500308C38B8AF000
WWPN=500308C38B8AF001
PORT=00000001
UNKN=00000000
WW2N=500308C38B8AF000
ATPN=HP Ultrium 4-SCSI C38B8AF000
Non-standard pages displayed only with -v parameter
cdi_info.drivestat is:
status = 0, DRIVE_STATUS_READY
msg = The tape drive is ready for use
Standard Inquiry data:
Vendor: HP
Product: Ultrium 4-SCSI
Rev: V61Z
VPD pages supported:
Pages 00 80 83 85 86 87 88 b0 b1 b2 c0 c1 c2 c3 c4 c5
Serial number page (80):
C38B8AF000
Device ID page (83):
WWNN=500308C38B8AF000
WWPN=500308C38B8AF001
PORT=00000001
UNKN=00000000
WW2N=500308C38B8AF000
ATPN=HP Ultrium 4-SCSI C38B8AF000
Non-standard pages displayed only with -v parameter
cdi_info.drivestat is:
status = 0, DRIVE_STATUS_READY
msg = The tape drive is ready for use
Standard Inquiry data:
Vendor: HP
Product: Ultrium 4-SCSI
Rev: V61Z
VPD pages supported:
Pages 00 80 83 85 86 87 88 b0 b1 b2 c0 c1 c2 c3 c4 c5
Serial number page (80):
C38B8AF000
Device ID page (83):
WWNN=500308C38B8AF000
WWPN=500308C38B8AF001
PORT=00000001
UNKN=00000000
WW2N=500308C38B8AF000
ATPN=HP Ultrium 4-SCSI C38B8AF000
Non-standard pages displayed only with -v parameter
cdi_info.drivestat is:
status = 0, DRIVE_STATUS_READY
msg = The tape drive is ready for use
[root@LPANWO01 by-id]# ^C
[root@LPANWO01 by-id]# cdi_inq -f scsi-3500308c38b8af004
Standard Inquiry data:
Vendor: HP
Product: Ultrium 4-SCSI
Rev: V61Z
VPD pages supported:
Pages 00 80 83 85 86 87 88 b0 b1 b2 c0 c1 c2 c3 c4 c5
Serial number page (80):
C38B8AF004
Device ID page (83):
WWNN=500308C38B8AF004
WWPN=500308C38B8AF005
PORT=00000001
UNKN=00000000
WW2N=500308C38B8AF004
ATPN=HP Ultrium 4-SCSI C38B8AF004
Non-standard pages displayed only with -v parameter
cdi_info.drivestat is:
status = 0, DRIVE_STATUS_READY
msg = The tape drive is ready for use
Standard Inquiry data:
Vendor: HP
Product: Ultrium 4-SCSI
Rev: V61Z
VPD pages supported:
Pages 00 80 83 85 86 87 88 b0 b1 b2 c0 c1 c2 c3 c4 c5
Serial number page (80):
C38B8AF004
Device ID page (83):
WWNN=500308C38B8AF004
WWPN=500308C38B8AF005
PORT=00000001
UNKN=00000000
WW2N=500308C38B8AF004
ATPN=HP Ultrium 4-SCSI C38B8AF004
Non-standard pages displayed only with -v parameter
cdi_info.drivestat is:
status = 0, DRIVE_STATUS_READY
msg = The tape drive is ready for use
So, I don't see why it can label the Tapes, or Inventory or do any task that I give from the Console.
Thanks in advance.
FQ
ble1
2 Intern
•
14.3K Posts
0
February 12th, 2015 10:00
How did you define drives? Over permanent or standard/legacy names? As your error came during loading and since it is not clear if you use persistent binding names, it might be that order used is not the one matching reality.
FQuintino
19 Posts
0
February 13th, 2015 02:00
Good morning Hrvoje,
Thank you for your answer.
If the name is permanent or standard defined ? How can I check that ?
I'm not using persistent binding names. And yes, after changing the tapes it was made a reboot on the library side and maybe it losted his path and that's why now it can't Label the Tapes.
At this moment my question is: Should I reinstall the Tape Library or there's a command or procedure to relink and teach, again, Networker to find the Path to the Physical Tape Library and Tape Drives ? It's so stupid that after 8 versions of Networker and 6 versions of Red Heat it stills needed to FIX A PATH and RESERVE NAMES to a device finds another !
Because a device reboot, and mainly on physical devices is not so unusual as it can it thinking.
Once again, Hrvoje, thank you for your valuable help and support.
With my best regards,
FQ
ble1
2 Intern
•
14.3K Posts
0
February 13th, 2015 03:00
You can check it by the name you have devices defined in NW. Normally, device on Linux you will find in /dev
[root@bzz dev]# ll nst*
crw-rw---- 1 root tape 9, 128 Apr 1 2014 nst0
crw-rw---- 1 root tape 9, 224 Apr 1 2014 nst0a
crw-rw---- 1 root tape 9, 160 Apr 1 2014 nst0l
crw-rw---- 1 root tape 9, 192 Apr 1 2014 nst0m
crw-rw---- 1 root tape 9, 129 Apr 1 2014 nst1
crw-rw---- 1 root tape 9, 225 Apr 1 2014 nst1a
crw-rw---- 1 root tape 9, 161 Apr 1 2014 nst1l
crw-rw---- 1 root tape 9, 193 Apr 1 2014 nst1m
crw-rw---- 1 root tape 9, 130 Mar 7 2014 nst2
crw-rw---- 1 root tape 9, 226 Mar 7 2014 nst2a
crw-rw---- 1 root tape 9, 162 Mar 7 2014 nst2l
crw-rw---- 1 root tape 9, 194 Mar 7 2014 nst2m
crw-rw---- 1 root tape 9, 131 Mar 7 2014 nst3
crw-rw---- 1 root tape 9, 227 Mar 7 2014 nst3a
crw-rw---- 1 root tape 9, 163 Mar 7 2014 nst3l
crw-rw---- 1 root tape 9, 195 Mar 7 2014 nst3m
What you see is 4 devices - each letter after number says about property of devices - you can google on that if interested more. These are normal names.
If you go to /dev/tape/by-id/ you will find so called persistent names, for example:
[root@bzz by-id]# ll
total 0
lrwxrwxrwx 1 root root 10 Apr 1 2014 scsi-1ADIC_A0C0120420_LLA -> ../../sg11
lrwxrwxrwx 1 root root 9 Apr 1 2014 scsi-3500308c0a0eaf000 -> ../../st0
lrwxrwxrwx 1 root root 10 Apr 1 2014 scsi-3500308c0a0eaf000-nst -> ../../nst0
lrwxrwxrwx 1 root root 9 Apr 1 2014 scsi-3500308c0a0eaf004 -> ../../st1
lrwxrwxrwx 1 root root 10 Apr 1 2014 scsi-3500308c0a0eaf004-nst -> ../../nst1
lrwxrwxrwx 1 root root 9 Mar 7 2014 scsi-3500308c0a0eaf090 -> ../../st2
lrwxrwxrwx 1 root root 10 Mar 7 2014 scsi-3500308c0a0eaf090-nst -> ../../nst2
lrwxrwxrwx 1 root root 9 Mar 7 2014 scsi-3500308c0a0eaf094 -> ../../st3
lrwxrwxrwx 1 root root 10 Mar 7 2014 scsi-3500308c0a0eaf094-nst -> ../../nst3
You will use nst names of course.
In NW, if you run jbcinfig -p you say you will use persistent names (and I think GUI method supports that too).
You can see what you use in NW now by simply checking which device names you have defined.
Do you have robotic and drives on the same box?
ble1
2 Intern
•
14.3K Posts
0
February 13th, 2015 04:00
ok, that seems to be ok. Now, take it to the next level. Do nsrjb -V and see what is the control port that you use. See if you can see the same via inquire. Do this on the host where devices are presented.
FQuintino
19 Posts
0
February 13th, 2015 04:00
[root@LPNWO01 ~]# nsrjb -V
1: 1QUANTUM_D1H0060819_LLA [enabled]
2: 1STK_L180_4519000000 [enabled]
No jukebox selected.
Please select a jukebox to use:? [1]
Configuration information for jukebox 1QUANTUM_D1H0060819_LLA:
model: Standard SCSI Jukebox
control port: /dev/tape/by-id/scsi-1QUANTUM_D1H0060819_LLA
bar code reader: Yes
jukebox features: elements_status volume_tags barcode autoeject no_trnsp ort_source_dest read_elem_unload_fail auto_inventory
number drives: 2
devices: /dev/tape/by-id/scsi-3500110a00104daf6-nst /dev/tape/by-id/scsi -3500308c38b8af004-nst
physical slots: 1-49
available slots: 1-49
operation timeout: 900 seconds
FQuintino
19 Posts
0
February 13th, 2015 04:00
Devices defined in NW, Checked.
[root@LNW01 dev]# ll nst*
crw-rw---- 1 root tape 9, 128 Feb 10 16:29 nst0
crw-rw---- 1 root tape 9, 224 Feb 10 16:29 nst0a
crw-rw---- 1 root tape 9, 160 Feb 10 16:29 nst0l
crw-rw---- 1 root tape 9, 192 Feb 10 16:29 nst0m
crw-rw---- 1 root tape 9, 129 Feb 10 16:29 nst1
crw-rw---- 1 root tape 9, 138 Feb 10 16:29 nst10
crw-rw---- 1 root tape 9, 234 Feb 10 16:29 nst10a
crw-rw---- 1 root tape 9, 170 Feb 10 16:29 nst10l
crw-rw---- 1 root tape 9, 202 Feb 10 16:29 nst10m
crw-rw---- 1 root tape 9, 139 Feb 10 16:29 nst11
crw-rw---- 1 root tape 9, 235 Feb 10 16:29 nst11a
crw-rw---- 1 root tape 9, 171 Feb 10 16:29 nst11l
crw-rw---- 1 root tape 9, 203 Feb 10 16:29 nst11m
crw-rw---- 1 root tape 9, 140 Feb 10 16:29 nst12
crw-rw---- 1 root tape 9, 236 Feb 10 16:29 nst12a
crw-rw---- 1 root tape 9, 172 Feb 10 16:29 nst12l
crw-rw---- 1 root tape 9, 204 Feb 10 16:29 nst12m
crw-rw---- 1 root tape 9, 141 Feb 10 16:29 nst13
crw-rw---- 1 root tape 9, 237 Feb 10 16:29 nst13a
crw-rw---- 1 root tape 9, 173 Feb 10 16:29 nst13l
crw-rw---- 1 root tape 9, 205 Feb 10 16:29 nst13m
crw-rw---- 1 root tape 9, 142 Feb 10 16:29 nst14
crw-rw---- 1 root tape 9, 238 Feb 10 16:29 nst14a
crw-rw---- 1 root tape 9, 174 Feb 10 16:29 nst14l
crw-rw---- 1 root tape 9, 206 Feb 10 16:29 nst14m
crw-rw---- 1 root tape 9, 143 Feb 10 16:29 nst15
crw-rw---- 1 root tape 9, 239 Feb 10 16:29 nst15a
crw-rw---- 1 root tape 9, 175 Feb 10 16:29 nst15l
crw-rw---- 1 root tape 9, 207 Feb 10 16:29 nst15m
crw-rw---- 1 root tape 9, 144 Feb 10 16:29 nst16
crw-rw---- 1 root tape 9, 240 Feb 10 16:29 nst16a
crw-rw---- 1 root tape 9, 176 Feb 10 16:29 nst16l
crw-rw---- 1 root tape 9, 208 Feb 10 16:29 nst16m
crw-rw---- 1 root tape 9, 145 Feb 10 16:29 nst17
crw-rw---- 1 root tape 9, 241 Feb 10 16:29 nst17a
crw-rw---- 1 root tape 9, 177 Feb 10 16:29 nst17l
crw-rw---- 1 root tape 9, 209 Feb 10 16:29 nst17m
crw-rw---- 1 root tape 9, 146 Feb 13 10:55 nst18
crw-rw---- 1 root tape 9, 242 Feb 13 10:55 nst18a
crw-rw---- 1 root tape 9, 178 Feb 13 10:55 nst18l
crw-rw---- 1 root tape 9, 210 Feb 13 10:55 nst18m
crw-rw---- 1 root tape 9, 147 Feb 13 10:55 nst19
crw-rw---- 1 root tape 9, 243 Feb 13 10:55 nst19a
crw-rw---- 1 root tape 9, 179 Feb 13 10:55 nst19l
crw-rw---- 1 root tape 9, 211 Feb 13 10:55 nst19m
crw-rw---- 1 root tape 9, 225 Feb 10 16:29 nst1a
crw-rw---- 1 root tape 9, 161 Feb 10 16:29 nst1l
crw-rw---- 1 root tape 9, 193 Feb 10 16:29 nst1m
crw-rw---- 1 root tape 9, 130 Feb 10 16:29 nst2
crw-rw---- 1 root tape 9, 226 Feb 10 16:29 nst2a
crw-rw---- 1 root tape 9, 162 Feb 10 16:29 nst2l
crw-rw---- 1 root tape 9, 194 Feb 10 16:29 nst2m
crw-rw---- 1 root tape 9, 131 Feb 10 16:29 nst3
crw-rw---- 1 root tape 9, 227 Feb 10 16:29 nst3a
crw-rw---- 1 root tape 9, 163 Feb 10 16:29 nst3l
crw-rw---- 1 root tape 9, 195 Feb 10 16:29 nst3m
crw-rw---- 1 root tape 9, 132 Feb 10 16:29 nst4
crw-rw---- 1 root tape 9, 228 Feb 10 16:29 nst4a
crw-rw---- 1 root tape 9, 164 Feb 10 16:29 nst4l
crw-rw---- 1 root tape 9, 196 Feb 10 16:29 nst4m
crw-rw---- 1 root tape 9, 133 Feb 10 16:29 nst5
crw-rw---- 1 root tape 9, 229 Feb 10 16:29 nst5a
crw-rw---- 1 root tape 9, 165 Feb 10 16:29 nst5l
crw-rw---- 1 root tape 9, 197 Feb 10 16:29 nst5m
crw-rw---- 1 root tape 9, 134 Feb 10 16:29 nst6
crw-rw---- 1 root tape 9, 230 Feb 10 16:29 nst6a
crw-rw---- 1 root tape 9, 166 Feb 10 16:29 nst6l
crw-rw---- 1 root tape 9, 198 Feb 10 16:29 nst6m
crw-rw---- 1 root tape 9, 135 Feb 10 16:29 nst7
crw-rw---- 1 root tape 9, 231 Feb 10 16:29 nst7a
crw-rw---- 1 root tape 9, 167 Feb 10 16:29 nst7l
crw-rw---- 1 root tape 9, 199 Feb 10 16:29 nst7m
crw-rw---- 1 root tape 9, 136 Feb 10 16:29 nst8
crw-rw---- 1 root tape 9, 232 Feb 10 16:29 nst8a
crw-rw---- 1 root tape 9, 168 Feb 10 16:29 nst8l
crw-rw---- 1 root tape 9, 200 Feb 10 16:29 nst8m
crw-rw---- 1 root tape 9, 137 Feb 10 16:29 nst9
crw-rw---- 1 root tape 9, 233 Feb 10 16:29 nst9a
crw-rw---- 1 root tape 9, 169 Feb 10 16:29 nst9l
crw-rw---- 1 root tape 9, 201 Feb 10 16:29 nst9m
Persistent names in NW, Checked.
[root@LNWO01 by-id]# ll
total 0
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000001 -> ../../st8
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000001-nst -> ../../nst8
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000002 -> ../../st0
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000002-nst -> ../../nst0
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000003 -> ../../st1
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000003-nst -> ../../nst1
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000004 -> ../../st2
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000004-nst -> ../../nst2
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000005 -> ../../st3
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000005-nst -> ../../nst3
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000006 -> ../../st4
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000006-nst -> ../../nst4
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000007 -> ../../st5
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000007-nst -> ../../nst5
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000008 -> ../../st6
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000008-nst -> ../../nst6
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000009 -> ../../st7
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000009-nst -> ../../nst7
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000A -> ../../st9
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000A-nst -> ../../nst9
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000B -> ../../st10
lrwxrwxrwx 1 root root 11 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000B-nst -> ../../nst10
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000C -> ../../st11
lrwxrwxrwx 1 root root 11 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000C-nst -> ../../nst11
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000D -> ../../st12
lrwxrwxrwx 1 root root 11 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000D-nst -> ../../nst12
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000E -> ../../st13
lrwxrwxrwx 1 root root 11 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000E-nst -> ../../nst13
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000F -> ../../st14
lrwxrwxrwx 1 root root 11 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_451900000F-nst -> ../../nst14
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000010 -> ../../st15
lrwxrwxrwx 1 root root 11 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000010-nst -> ../../nst15
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000011 -> ../../st16
lrwxrwxrwx 1 root root 11 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000011-nst -> ../../nst16
lrwxrwxrwx 1 root root 10 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000012 -> ../../st17
lrwxrwxrwx 1 root root 11 Feb 10 16:29 scsi-1IBM_ULTRIUM-TD3_4519000012-nst -> ../../nst17
lrwxrwxrwx 1 root root 10 Feb 13 10:55 scsi-1QUANTUM_D1H0060819_LLA -> ../../sg26
lrwxrwxrwx 1 root root 9 Feb 10 16:29 scsi-1STK_L180_4519000000 -> ../../sg3
lrwxrwxrwx 1 root root 10 Feb 13 10:55 scsi-3500308c38b8af000 -> ../../st18
lrwxrwxrwx 1 root root 11 Feb 13 10:55 scsi-3500308c38b8af000-nst -> ../../nst18
lrwxrwxrwx 1 root root 10 Feb 13 10:55 scsi-3500308c38b8af004 -> ../../st19
lrwxrwxrwx 1 root root 11 Feb 13 10:55 scsi-3500308c38b8af004-nst -> ../../nst19
The scope of the problem (Tape Library Quantum and Tape Drives associated to this Library):
lrwxrwxrwx 1 root root 10 Feb 13 10:55 scsi-1QUANTUM_D1H0060819_LLA -> ../../sg26
lrwxrwxrwx 1 root root 10 Feb 13 10:55 scsi-3500308c38b8af000 -> ../../st18
lrwxrwxrwx 1 root root 11 Feb 13 10:55 scsi-3500308c38b8af000-nst -> ../../nst18
lrwxrwxrwx 1 root root 10 Feb 13 10:55 scsi-3500308c38b8af004 -> ../../st19
lrwxrwxrwx 1 root root 11 Feb 13 10:55 scsi-3500308c38b8af004-nst -> ../../nst19
And Yes, Robotic and Drives are on the same Box.
So, correct me if i'm wrong, the Devices are configured with persistent names, right ?
And this is what I see at the GUI
So, I still don't uderstand what's wrong.
Thank you.
Best regards,
FQ
FQuintino
19 Posts
0
February 13th, 2015 04:00
Now looking better, I see a diference on Drives Names.
CLI Console Networker Management Consola
scsi-3500308c38b8af000-nst /dev/tape/by-id/scsi-3500110a00104daf6-nst
scsi-3500308c38b8af004-nst /dev/tape/by-id/scsi-3500308c38b8af004-nst
ble1
2 Intern
•
14.3K Posts
1
February 13th, 2015 05:00
It doesn't matter from where you delete it - I think it is easier from GUI.
jbconfig you can do from CLI - just make sure to run jbconfig -p (as -p means you will use persistent names).
FQuintino
19 Posts
0
February 13th, 2015 05:00
Hi Hrvoje,
It's the same Host, Networker Server. Through Putty I connect with a SSH Session.
They display two different things, maybe because Networker Management Console has cache info on the API ?
It real reads the nsrdb when I Launch the Networker open the Networker Management Console ?
Evidences says me, NO.
Now, if theres no chance to reconfigure the correct Drive to the Management Console see it or recheck the right drives to reconnect and I will delete the Library and the devices related to this Library, should I delete from the CLI Console or the NMC ?
I mean, should I reconfigure through the CLI or the NMC ?
Thank you again,
FQ
FQuintino
19 Posts
0
February 13th, 2015 08:00
I've deleted tghe Libraries and the Drives through the Networker.
Now I used jbconfig -p and reconfigured the Tape Library (asking me for the name for the Jukebox I gived the same name identified 1QUANTUM_D1H0060819_LLA).
Answer allways default at the questions. The drives were detected and now they are right at the NMC.
But now I need to create the Parent Jukebox and affiliate this drives to the Jukebox.
Can you help me to finalize this please ?
Best Regards,
FQ
a) make sure drives are not loaded [Done]
b) delete lib in NW [Done]
c) delete devices for this lib in NW [Done]
d) configure it again
e) check device paths
FQuintino
19 Posts
0
February 13th, 2015 08:00
nsrjb -V
1: 1STK_L180_4519000000 [enabled]
There is only one enabled and configured jukebox: 1STK_L180_4519000000
Configuration information for jukebox 1STK_L180_4519000000:
model: Standard SCSI Jukebox
control port: /dev/tape/by-id/scsi-1STK_L180_4519000000
bar code reader: Yes
ble1
2 Intern
•
14.3K Posts
0
February 13th, 2015 08:00
Parent jukebox? Sorry, but what are you talking about? jbconfig configures jukebox and associated drives.