cancel
Showing results for 
Search instead for 
Did you mean: 

 Yes, please read my

 

Yes, please read my post.

 

TLD(3) is the library I think was having the problem - you confirmed this.

If you look at the scan output, you will see this library is not listing any drives.  This is incorrect, and is a problem with either the configeration, or a fault, on that library.

It is all explained in my other post.

 

It might be work power cycling the library, that can sometimes fix issues like this.

Martin

Yes, please read my

 

 

Yes, please read my post.

 

TLD(3) is the library I think was having the problem - you confirmed this.

If you look at the scan output, you will see this library is not listing any drives.  This is incorrect, and is a problem with either the configeration, or a fault, on that library.

It is all explained in my other post.

 

It might be work power cycling the library, that can sometimes fix issues like this.

Martin

case update

hi ,

finally we find a mechanical issue with STK sl3000 tape library and we are working with support

now the library is working ,but from the side of the NB i want the correct steps to see all drives and the media servers to  to see the robots  can you please give me the commands and steps to do that  ..thnx

also if there is still in

also if there is still in device monitor drives is down ..how to up all it 

is restarting daemons on master and media servers the correct way to scan the tape library changes

Whenever I see a library

Whenever I see a library down, restarting ltid seems to fix it ...

If you right click the drives, you can select the 'up' drives option.

Only the 'robot control host' will see the robot, the other media servers don't actually see it (or shouldn't).

tpautoconf -r (from the robot control host) will show and lilbraries that are attached.

tpautoconf -t (from any media server with drives) should show the tape drives that are visible.

Or, just run scan command

This commnads only send scsi commands to the devices visiable in the OS, so if they don't work, then the issue is outside NBU.

tpautoconf -d shows what is configured in NBU.  You can run this on each media server.

NOTE.

I can configure a drive that doesn't exsist if I want to.  This will appear in tpconfig -d but won't work of course.  Therefore, do NOT use tpconfig -d to troubleshoot connectivity / hardware issues, it's useless, use tpautoconf (or scan),

All these commands are in /usr/openv/volmgr/bin

Restarting services does't scan for changes.  If the hardware config has changed, you need to run the device wizard.  It may be necessary to rebuild the pass-thru driver, depening on the OS type.  Before running the device wizard, it may be necessary to delete the devices.

This is ALL covered in the NBU manuals.

TN on running the Device Wizard

http://www.symantec.com/docs/TECH125956

 

Martin

hi martin, thank you for the

hi martin,

thank you for the Device Configuration link ok i already run  Device Configuration Wizard, but still i see the output of tpconfig -d on master server that there is down pathes although i initiated a backup to library and it run correctly

you mean by  (from the robot control host) from the media server that use the tape library or master server  running  tpautoconf -r ??

and can you please till me the scan command  and its path to run it?

 

Can you post tpconfig -d

Can you post tpconfig -d output to us?

you mean by  (from the robot

you mean by  (from the robot control host) from the media server that use the tape library or master server  running  tpautoconf -r ??

Yes,

scan is in /usr/openv/volmgr/bin

I think you said the os was

I think you said the os was HP.

Do you see all the tape drive as 'claimed' in ioscan:

ioscan -kfnCtape

the o/p output of tpconfig -d

the o/p

output of tpconfig -d on master server

Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   Drive000             4mm    Standalone
      MISSING_PATH:MISSING_PATH:MISSING_PATH:MISSING_PATH:MISSING_PATH DISABLED
      MISSING_PATH:MISSING_PATH:MISSING_PATH:MISSING_PATH:MISSING_PATH DISABLED
1   HP.C7438A.000        4mm    Standalone
      /dev/rtape/tape1_BESTnb                                          DISABLED
2   HP.ULTRIUM3-SCSI.123 hcart3 Standalone
      /dev/rmt/c3t4d0BESTnb                                            DISABLED
3   sl3k_m4_12           hcart  TLD(3)  DRIVE=12
      /dev/rtape/tape214_BESTnb                                        UP
4   HP.ULTRIUM3-SCSI.000 hcart3 TLD(2)  DRIVE=1
      /dev/rtape/tape65_BESTnb                                         UP
5   HP.ULTRIUM3-SCSI.001 hcart3 TLD(2)  DRIVE=2
      /dev/rtape/tape66_BESTnb                                         UP
6   HP.ULTRIUM3-SCSI.002 hcart3 TLD(2)  DRIVE=3
      /dev/rtape/tape67_BESTnb                                         UP
7   HP.ULTRIUM3-SCSI.003 hcart3 TLD(2)  DRIVE=4
      /dev/rtape/tape68_BESTnb                                         UP
8   HP.ULTRIUM3-SCSI.004 hcart3 TLD(2)  DRIVE=5
      /dev/rtape/tape69_BESTnb                                         UP
9   HP.ULTRIUM3-SCSI.005 hcart3 TLD(2)  DRIVE=6
      /dev/rtape/tape70_BESTnb                                         UP
10  HP.ULTRIUM3-SCSI.006 hcart3 TLD(2)  DRIVE=7
      /dev/rtape/tape71_BESTnb                                         UP
11  HP.ULTRIUM3-SCSI.007 hcart3 TLD(2)  DRIVE=8
      /dev/rtape/tape72_BESTnb                                         UP
12  HP.ULTRIUM3-SCSI.008 hcart3 TLD(2)  DRIVE=9
      /dev/rtape/tape73_BESTnb                                         UP
13  HP.ULTRIUM3-SCSI.009 hcart3 TLD(2)  DRIVE=10
      /dev/rtape/tape74_BESTnb                                         UP
14  HP.ULTRIUM3-SCSI.010 hcart3 TLD(2)  DRIVE=11
      /dev/rtape/tape75_BESTnb                                         UP
15  HP.ULTRIUM3-SCSI.011 hcart3 TLD(2)  DRIVE=12
      /dev/rtape/tape76_BESTnb                                         UP
16  HP.ULTRIUM3-SCSI.012 hcart3 TLD(2)  DRIVE=13
      /dev/rtape/tape77_BESTnb                                         UP
17  HP.ULTRIUM3-SCSI.013 hcart3 TLD(2)  DRIVE=14
      /dev/rtape/tape78_BESTnb                                         UP
18  HP.ULTRIUM3-SCSI.014 hcart3 TLD(2)  DRIVE=15
      /dev/rtape/tape79_BESTnb                                         UP
19  HP.ULTRIUM3-SCSI.015 hcart3 TLD(2)  DRIVE=16
      /dev/rtape/tape80_BESTnb                                         UP
20  HP.ULTRIUM3-SCSI.016 hcart3 TLD(2)  DRIVE=17
      /dev/rtape/tape81_BESTnb                                         UP
21  HP.ULTRIUM3-SCSI.017 hcart3 TLD(2)  DRIVE=18
      /dev/rtape/tape82_BESTnb                                         UP
22  HP.ULTRIUM3-SCSI.018 hcart3 TLD(2)  DRIVE=19
      /dev/rtape/tape83_BESTnb                                         UP
23  HP.ULTRIUM3-SCSI.019 hcart3 TLD(2)  DRIVE=20
      /dev/rtape/tape84_BESTnb                                         UP
24  IBM.ULTRIUM-TD3.000  hcart3 TLD(1)  DRIVE=1
      /dev/rtape/tape85_BESTnb                                         UP
25  IBM.ULTRIUM-TD3.001  hcart3 TLD(1)  DRIVE=2
      /dev/rtape/tape86_BESTnb                                         UP
26  IBM.ULTRIUM-TD3.002  hcart3 TLD(1)  DRIVE=3
      /dev/rtape/tape87_BESTnb                                         UP
27  IBM.ULTRIUM-TD3.003  hcart3 TLD(1)  DRIVE=4
      /dev/rtape/tape88_BESTnb                                         UP
28  IBM.ULTRIUM-TD3.004  hcart3 TLD(1)  DRIVE=5
      /dev/rtape/tape89_BESTnb                                         UP
29  IBM.ULTRIUM-TD3.005  hcart3 TLD(1)  DRIVE=6
      /dev/rtape/tape90_BESTnb                                         UP
30  IBM.ULTRIUM-TD3.006  hcart3 TLD(1)  DRIVE=7
      /dev/rtape/tape91_BESTnb                                         UP
31  IBM.ULTRIUM-TD3.007  hcart3 TLD(1)  DRIVE=8
      /dev/rtape/tape92_BESTnb                                         UP
32  IBM.ULTRIUM-TD3.008  hcart3 TLD(1)  DRIVE=9
      /dev/rtape/tape93_BESTnb                                         UP
33  IBM.ULTRIUM-TD3.009  hcart3 TLD(1)  DRIVE=10
      /dev/rtape/tape94_BESTnb                                         UP
34  IBM.ULTRIUM-TD3.010  hcart3 TLD(1)  DRIVE=11
      /dev/rtape/tape95_BESTnb                                         UP
35  IBM.ULTRIUM-TD3.011  hcart3 TLD(1)  DRIVE=12
      /dev/rtape/tape96_BESTnb                                         UP
36  IBM.ULTRIUM-TD3.012  hcart3 TLD(1)  DRIVE=13
      /dev/rtape/tape97_BESTnb                                         UP
37  IBM.ULTRIUM-TD3.013  hcart3 TLD(1)  DRIVE=14
      /dev/rtape/tape98_BESTnb                                         UP
38  IBM.ULTRIUM-TD3.014  hcart3 TLD(1)  DRIVE=15
      /dev/rtape/tape99_BESTnb                                         UP
39  IBM.ULTRIUM-TD3.015  hcart3 TLD(1)  DRIVE=16
      /dev/rtape/tape100_BESTnb                                        UP
40  IBM.ULTRIUM-TD3.016  hcart3 TLD(1)  DRIVE=17
      /dev/rtape/tape101_BESTnb                                        UP
41  IBM.ULTRIUM-TD3.017  hcart3 TLD(1)  DRIVE=18
      /dev/rtape/tape102_BESTnb                                        UP
42  IBM.ULTRIUM-TD3.018  hcart3 TLD(1)  DRIVE=19
      /dev/rtape/tape103_BESTnb                                        UP
43  IBM.ULTRIUM-TD3.019  hcart3 TLD(1)  DRIVE=20
      /dev/rtape/tape104_BESTnb                                        UP
44  IBM.ULTRIUM-TD3.020  hcart3 TLD(1)  DRIVE=21
      /dev/rtape/tape105_BESTnb                                        UP
45  IBM.ULTRIUM-TD3.021  hcart3 TLD(1)  DRIVE=22
      /dev/rtape/tape106_BESTnb                                        UP
46  IBM.ULTRIUM-TD3.022  hcart3 TLD(1)  DRIVE=23
      /dev/rtape/tape107_BESTnb                                        UP
47  IBM.ULTRIUM-TD3.023  hcart3 TLD(1)  DRIVE=24
      /dev/rtape/tape108_BESTnb                                        UP
48  IBM.ULTRIUM-TD3.024  hcart3 TLD(1)  DRIVE=25
      /dev/rtape/tape109_BESTnb                                        UP
49  IBM.ULTRIUM-TD3.025  hcart3 TLD(1)  DRIVE=26
      /dev/rtape/tape110_BESTnb                                        UP
50  IBM.ULTRIUM-TD3.026  hcart3 TLD(1)  DRIVE=27
      /dev/rtape/tape111_BESTnb                                        UP
51  IBM.ULTRIUM-TD3.027  hcart3 TLD(1)  DRIVE=28
      /dev/rtape/tape112_BESTnb                                        UP
52  IBM.ULTRIUM-TD3.028  hcart3 TLD(1)  DRIVE=29
      /dev/rtape/tape113_BESTnb                                        UP
53  IBM.ULTRIUM-TD3.029  hcart3 TLD(1)  DRIVE=30
      /dev/rtape/tape114_BESTnb                                        UP
54  sl3k_m4_11           hcart  TLD(3)  DRIVE=11
      /dev/rtape/tape213_BESTnb                                        UP
55  sl3k_m4_10           hcart  TLD(3)  DRIVE=10
      /dev/rtape/tape212_BESTnb                                        UP
56  sl3k_m4_16           hcart  TLD(3)  DRIVE=16
      /dev/rtape/tape217_BESTnb                                        UP
57  sl3k_m4_13           hcart  TLD(3)  DRIVE=13
      /dev/rtape/tape215_BESTnb                                        UP
58  sl3k_m4_14           hcart  TLD(3)  DRIVE=14
      /dev/rtape/tape146_BESTnb                                        UP
59  sl3k_m4_09           hcart  TLD(3)  DRIVE=9
      /dev/rtape/tape218_BESTnb                                        UP
60  IBM.ULTRIUM-TD3.030  hcart3 TLD(1)  DRIVE=31
      /dev/rtape/tape115_BESTnb                                        UP
61  sl3k_m4_15           hcart  TLD(3)  DRIVE=15
      /dev/rtape/tape216_BESTnb                                        UP
62  sl3k_aixback_06      hcart  TLD(3)  DRIVE=6
      /dev/rtape/tape211_BESTnb                                        DOWN
82  t10k_m4_d17          hcart3 TLD(3)  DRIVE=18
      /dev/rtape/tape149_BESTnb                                        UP
83  t10k_m4_d18          hcart3 TLD(3)  DRIVE=18
      /dev/rmt/c160t0d0BESTnb                                          UP
86  IBM.ULTRIUM-TD3.051  hcart3 TLD(9)  DRIVE=1
      /dev/rtape/tape191_BESTnb                                        DOWN
87  IBM.ULTRIUM-TD3.052  hcart3 TLD(9)  DRIVE=2
      /dev/rtape/tape192_BESTnb                                        DOWN
88  IBM.ULTRIUM-TD3.073  hcart3 TLD(9)  DRIVE=3
      /dev/rtape/tape193_BESTnb                                        UP
89  IBM.ULTRIUM-TD3.074  hcart3 TLD(9)  DRIVE=4
      /dev/rtape/tape194_BESTnb                                        UP
90  IBM.ULTRIUM-TD3.075  hcart3 TLD(9)  DRIVE=5
      /dev/rtape/tape195_BESTnb                                        UP
91  IBM.ULTRIUM-TD3.076  hcart3 TLD(9)  DRIVE=6
      /dev/rtape/tape196_BESTnb                                        UP
92  IBM.ULTRIUM-TD3.077  hcart3 TLD(9)  DRIVE=7
      /dev/rtape/tape197_BESTnb                                        UP
93  IBM.ULTRIUM-TD3.078  hcart3 TLD(9)  DRIVE=8
      /dev/rtape/tape198_BESTnb                                        UP
94  IBM.ULTRIUM-TD3.079  hcart3 TLD(9)  DRIVE=9
      /dev/rtape/tape199_BESTnb                                        UP
95  IBM.ULTRIUM-TD3.080  hcart3 TLD(9)  DRIVE=10
      /dev/rtape/tape200_BESTnb                                        UP
96  IBM.ULTRIUM-TD3.081  hcart3 TLD(9)  DRIVE=11
      /dev/rtape/tape201_BESTnb                                        UP
97  IBM.ULTRIUM-TD3.082  hcart3 TLD(9)  DRIVE=12
      /dev/rtape/tape202_BESTnb                                        UP
98  IBM.ULTRIUM-TD3.083  hcart3 TLD(9)  DRIVE=13
      /dev/rtape/tape203_BESTnb                                        UP
99  IBM.ULTRIUM-TD3.084  hcart3 TLD(9)  DRIVE=14
      /dev/rtape/tape204_BESTnb                                        UP
100 IBM.ULTRIUM-TD3.085  hcart3 TLD(9)  DRIVE=15
      /dev/rtape/tape205_BESTnb                                        UP
101 IBM.ULTRIUM-TD3.086  hcart3 TLD(9)  DRIVE=16
      /dev/rtape/tape206_BESTnb                                        UP
102 IBM.ULTRIUM-TD3.087  hcart3 TLD(9)  DRIVE=17
      /dev/rtape/tape207_BESTnb                                        UP
103 IBM.ULTRIUM-TD3.088  hcart3 TLD(9)  DRIVE=18
      /dev/rtape/tape208_BESTnb                                        UP
104 IBM.ULTRIUM-TD3.089  hcart3 TLD(9)  DRIVE=19
      /dev/rtape/tape209_BESTnb                                        UP
105 IBM.ULTRIUM-TD3.090  hcart3 TLD(9)  DRIVE=20
      /dev/rtape/tape210_BESTnb                                        UP

Currently defined robotics are:
  TLD(1)     robotic path = /dev/rchgr/autoch4
  TLD(2)     robotic path = /dev/rchgr/autoch3
  TLD(3)     robotic path = /dev/rchgr/autoch5
  TLD(9)     robotic path = /dev/rchgr/autoch10

EMM Server = RHC4


But if you look at  "/dev/rchgr/autoch5"   ( tld(3) ) can you see that iit does not show any drives listed.

 

yes for master or the media

yes for master or the media

It will be on both, but you

It will be on both, but you only run it on servers that have devices attached.

(I'm referring to the scan command)

M

Moved:

Re: Which Unix OS?Can the OS