Robtest does not show a robot

[blanco_adalbert]

Hello Every body, I have a situation where tpconfig -l / -d  command show me the whole robots i have attached to a master server, but when i run the robtest command it shows only two of the three robots attached.

I have reinstalled the sg.drivers lots of times and restarted the netbackup services bit it continues showing only two. Also I have used the command tldtest -r /path of fobot and it works.

What i am doing grong.....

this is the output ot the commands.

Device Robot Drive       Robot                    Drive                 Device          Second
Type     Num Index  Type DrNum Status  Comment    Name                  Path            Device Path
robot      0    -    TLD    -       -  -          -                     /dev/sg/c0tw500104f000ba6017l0
  drive    -    1  hcart    2      UP  -          IBM.ULTRIUM-TD4.004   /dev/rmt/0cbn
  drive    -    2  hcart    3      UP  -          IBM.ULTRIUM-TD4.005   /dev/rmt/9cbn
  drive    -    3  hcart    4      UP  -          IBM.ULTRIUM-TD4.006   /dev/rmt/1cbn
  drive    -    4  hcart    5      UP  -          IBM.ULTRIUM-TD4.007   /dev/rmt/10cbn
  drive    -    5  hcart    6      UP  -          IBM.ULTRIUM-TD4.008   /dev/rmt/2cbn
  drive    -    6    dlt    8      UP  -          QUANTUM.SDLT600.000   /dev/rmt/4cbn
  drive    -   11  hcart    1      UP  -          IBM.ULTRIUM-TD4.010   /dev/rmt/8cbn
robot      1    -    TLD    -       -  -          -                     /dev/sg/c0tw2101000d779ae30fl0
  drive    -    0  hcart    1      UP  -          IBM.ULTRIUM-TD4.000   /dev/rmt/23cbn
  drive    -   12  hcart   10      UP  -          IBM.ULTRIUM-TD4.015   /dev/rmt/14cbn
  drive    -   13  hcart   11      UP  -          IBM.ULTRIUM-TD4.018   /dev/rmt/13cbn
  drive    -   14  hcart   12      UP  -          IBM.ULTRIUM-TD4.017   /dev/rmt/12cbn
  drive    -   15  hcart   13      UP  -          IBM.ULTRIUM-TD4.016   /dev/rmt/11cbn
  drive    -   16  hcart    2      UP  -          IBM.ULTRIUM-TD4.001   /dev/rmt/22cbn
  drive    -   17  hcart    3      UP  -          IBM.ULTRIUM-TD4.002   /dev/rmt/21cbn
  drive    -   18  hcart    4      UP  -          IBM.ULTRIUM-TD4.003   /dev/rmt/20cbn
  drive    -   19  hcart    5      UP  -          IBM.ULTRIUM-TD4.009   /dev/rmt/19cbn
  drive    -   20  hcart    6      UP  -          IBM.ULTRIUM-TD4.011   /dev/rmt/18cbn
  drive    -   21  hcart    7      UP  -          IBM.ULTRIUM-TD4.012   /dev/rmt/17cbn
  drive    -   22  hcart    8      UP  -          IBM.ULTRIUM-TD4.013   /dev/rmt/16cbn
  drive    -   23  hcart    9      UP  -          IBM.ULTRIUM-TD4.014   /dev/rmt/15cbn
robot      2    -    TLD    -       -  -          -                     /dev/sg/c0tw500104f000cd8583l1
  drive    -    7 hcart2    1      UP  -          HP.ULTRIUM5-SCSI.000  /dev/rmt/5cbn
  drive    -    8 hcart2    2      UP  -          HP.ULTRIUM5-SCSI.001  /dev/rmt/3cbn
  drive    -    9 hcart2    3      UP  -          HP.ULTRIUM5-SCSI.002  /dev/rmt/6cbn
  drive    -   10 hcart2    4      UP  -          HP.ULTRIUM5-SCSI.003  /dev/rmt/7cbn
 

root@nbu:/usr/openv/volmgr/bin/driver# robtest
Configured robots with local control supporting test utilities:
  TLD(0)     robotic path = /dev/sg/c0tw500104f000ba6017l0
  TLD(1)     robotic path = /dev/sg/c0tw2101000d779ae30fl0

Robot Selection
---------------
  1)  TLD 0
  2)  TLD 1
  3)  none/quit
 

root@nbu:/usr/openv/volmgr/bin/driver# tldtest -r /dev/sg/c0tw500104f000cd8583l1
Opening /dev/sg/c0tw500104f000cd8583l1
MODE_SENSE complete
Enter tld commands (? returns help information)
s d
drive 1 (addr 500) access = 1 Contains Cartridge = no
drive 2 (addr 501) access = 1 Contains Cartridge = no
drive 3 (addr 502) access = 1 Contains Cartridge = no
drive 4 (addr 503) access = 1 Contains Cartridge = no
READ_ELEMENT_STATUS complete
 

[revarooo]

Let's see the tpconfig -d output, perhaps the other robot is under robot control on a different server?

[blanco_adalbert]

Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   IBM.ULTRIUM-TD4.000  hcart  TLD(1)  DRIVE=1
      /dev/rmt/23cbn                                                   UP
1   IBM.ULTRIUM-TD4.004  hcart  TLD(0)  DRIVE=2
      /dev/rmt/0cbn                                                    UP
2   IBM.ULTRIUM-TD4.005  hcart  TLD(0)  DRIVE=3
      /dev/rmt/9cbn                                                    UP
3   IBM.ULTRIUM-TD4.006  hcart  TLD(0)  DRIVE=4
      /dev/rmt/1cbn                                                    UP
4   IBM.ULTRIUM-TD4.007  hcart  TLD(0)  DRIVE=5
      /dev/rmt/10cbn                                                   UP
5   IBM.ULTRIUM-TD4.008  hcart  TLD(0)  DRIVE=6
      /dev/rmt/2cbn                                                    UP
6   QUANTUM.SDLT600.000  dlt    TLD(0)  DRIVE=8
      /dev/rmt/4cbn                                                    UP
7   HP.ULTRIUM5-SCSI.000 hcart2 TLD(2)  DRIVE=1
      /dev/rmt/5cbn                                                    UP
8   HP.ULTRIUM5-SCSI.001 hcart2 TLD(2)  DRIVE=2
      /dev/rmt/3cbn                                                    UP
9   HP.ULTRIUM5-SCSI.002 hcart2 TLD(2)  DRIVE=3
      /dev/rmt/6cbn                                                    UP
10  HP.ULTRIUM5-SCSI.003 hcart2 TLD(2)  DRIVE=4
      /dev/rmt/7cbn                                                    UP
11  IBM.ULTRIUM-TD4.010  hcart  TLD(0)  DRIVE=1
      /dev/rmt/8cbn                                                    UP
12  IBM.ULTRIUM-TD4.015  hcart  TLD(1)  DRIVE=10
      /dev/rmt/14cbn                                                   UP
13  IBM.ULTRIUM-TD4.018  hcart  TLD(1)  DRIVE=11
      /dev/rmt/13cbn                                                   UP
14  IBM.ULTRIUM-TD4.017  hcart  TLD(1)  DRIVE=12
      /dev/rmt/12cbn                                                   UP
15  IBM.ULTRIUM-TD4.016  hcart  TLD(1)  DRIVE=13
      /dev/rmt/11cbn                                                   UP
16  IBM.ULTRIUM-TD4.001  hcart  TLD(1)  DRIVE=2
      /dev/rmt/22cbn                                                   UP
17  IBM.ULTRIUM-TD4.002  hcart  TLD(1)  DRIVE=3
      /dev/rmt/21cbn                                                   UP
18  IBM.ULTRIUM-TD4.003  hcart  TLD(1)  DRIVE=4
      /dev/rmt/20cbn                                                   UP
19  IBM.ULTRIUM-TD4.009  hcart  TLD(1)  DRIVE=5
      /dev/rmt/19cbn                                                   UP
20  IBM.ULTRIUM-TD4.011  hcart  TLD(1)  DRIVE=6
      /dev/rmt/18cbn                                                   UP
21  IBM.ULTRIUM-TD4.012  hcart  TLD(1)  DRIVE=7
      /dev/rmt/17cbn                                                   UP
22  IBM.ULTRIUM-TD4.013  hcart  TLD(1)  DRIVE=8
      /dev/rmt/16cbn                                                   UP
23  IBM.ULTRIUM-TD4.014  hcart  TLD(1)  DRIVE=9
      /dev/rmt/15cbn                                                   UP

Currently defined robotics are:
  TLD(0)     robotic path = /dev/sg/c0tw500104f000ba6017l0
  TLD(1)     robotic path = /dev/sg/c0tw2101000d779ae30fl0
  TLD(2)     robotic path = /dev/sg/c0tw500104f000cd8583l1

[blanco_adalbert]

Also when I try to inventory the robot I get the error mesage, robot does not exist (214)

and the status of the robot is enabled = no.

how can i enable the robot?

is this error a license related option?

[Will_Restore]

Try running the Device Configuration Wizard again

[blanco_adalbert]

I run the Device Configuration Wizard, it detects the three robot libraries and if finishes without error.

I try to run an inventory but I got the 214 error

[blanco_adalbert]

I have found this information with a tpconfig -emm_dev_list

Robot:                          ROBOT2
Robot Number:                   2
Robot Type:                     PCR(4)
Media Server:                   nbu
Port:                           -1
Bus:                            -1
Target:                         -1
Lun:                            -1
PartiallyConfigured:            1
Pird:                           0
Host:                           -
Apath:                          /dev/sg/c0tw500104f000cd8583l1
NDMP Attach Host:               -
VMhost:                         nbu
DAhost:                         nbu
SN:                             464970G+1323SY1043
Inquiry:                        STK     SL150           0200
WorldWideId:                    -
Old DAhost:                     nbu
RSM GUID:                       00000000-0000-0000-0000-000000000000
 

why the robot is detected as a pcr type?

[mph999]

pcr type, no idea, i fact, I've never seen that before.

Is the robot the same type as the others, in fact, could you let us know the exact make/ model of all the libraries, and confirm which is the problem one.

I seen the robot comes back in the command as STK SL150 which is a tld type.  Could you confirm this is the correct model.  

Also, is this a physical library, or VTL.

In fact this TN  http://www.symantec.com/docs/HOWTO32973 

... does not even mention a PCR type - odd ..., well I guess this could be the issue.

What version of NBU are you running.

On the wizard screen, the bit where you see the libraries and the tape drives, if you left click on the library/ changer, there is a properties button, if you click this, does it give you the ability to  change the robot type to TLD ?

Also, can you run these commands and post the output, again, please show which is the problem robot.

/usr/openv/volmgr/bin/scsi_command -d <path to robot>

(The path to each robot can be seen above at the bottom of the tpconfig -d command you posted.  Apologies, I'm on an ipad and it won't let me copy/ paste for some reason.

Eg.  /usr/openv/volmgr/bin/scsi_command -d /dev/sg/C0tw500....

Do this for each path.

This at first glance looks a bit like a rare case where updating the device mappings files would work, but if the libraries are the same type then that won't be the cause, as it would be broken for all of them.  Also, the SL150 is common and I can't honestly see the device mappings file being messed up for it.

[blanco_adalbert]

Hello,

the correct model for the robot library is SL150, also I have run the Device Configuration Wizard and i have chaned the robot type to TLD and the device configuration manager finishes without warning and / or error.

the netbackup version i am running is 7.5.0.3

this is the output of the scsi_command

root@nbu:/usr/openv/volmgr/bin/driver# scsi_command -d /dev/sg/c0tw500104f000cd8583l1
Inquiry data: removable dev type 8h STK     SL150           0200
 

root@nbu:/usr/openv/volmgr/bin/driver# scsi_command -d /dev/sg/c0tw2101000d779ae30fl0
Inquiry data: removable dev type 8h STK     L700            3.05
 

root@nbu:/usr/openv/volmgr/bin/driver# scsi_command -d /dev/sg/c0tw500104f000ba6017l0
Inquiry data: removable dev type 8h STK     SL500           1373
 

I have worked with the SL150 Library before and this is the first time i have problems when configuring the library.

[blanco_adalbert]

Hello i have run the following command tpconfig -emm_dev_list and it show that the robot is partially configured, does any body knows what it referes to?

Robot:                          ROBOT2
Robot Number:                   2
Robot Type:                     TLD(8)
Media Server:                   nbu
Port:                           -1
Bus:                            -1
Target:                         -1
Lun:                            -1
PartiallyConfigured:            1
Pird:                           0
Host:                           -
Apath:                          /dev/sg/c0tw500104f000cd8583l1
NDMP Attach Host:               -
VMhost:                         nbu
DAhost:                         nbu
SN:                             464970G+1323SY1043
Inquiry:                        STK     SL150           0200
WorldWideId:                    -
Old DAhost:                     nbu
RSM GUID:                       00000000-0000-0000-0000-000000000000
 

[blanco_adalbert]

this is the output of the scan command

------------------------------------------------------------
Device Name  : "/dev/sg/c0tw500104f000cd8583l1"
Passthru Name: "/dev/sg/c0tw500104f000cd8583l1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "STK     SL150           0200"
Vendor ID  : "STK     "
Product ID : "SL150           "
Product Rev: "0200"
Serial Number: "464970G+1323SY1043"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "STK     SL150           464970G+1323SY1043"
Device Type    : SDT_CHANGER
NetBackup Robot Type: Not Found(5)
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 4
Number of Slots  : 90
Number of Media Access Ports: 4
Drive 1 Serial Number      : "HU1313V65J"
Drive 2 Serial Number      : "HU1315VE0F"
Drive 3 Serial Number      : "HU1313V66Y"
Drive 4 Serial Number      : "HU1315VDYG"
Flags : 0x0
Reason: 0x0
 

[blanco_adalbert · Accepted solution]

I have solved the issue.

The solution was to delete all drives and robots, then register robots manually and running the device configuration manager from the master server.

tpconfig -add -robot 2 -robtype tld -robpath /dev/sg/c0tw500104f000cd8583l1
 

Best regards

[mph999]

Good to hear you have it working.

Manual config is fine, but hasn't actually solved the issue as to why the wizard doesn't work.  However, if you are happy with this then of course that is fine.

NBU Robot type : Not found in the scan output is interesting, not sure why.  I see the other two robots are a different model, so I think in this case I would install the latest devce mappings files and see if that resolves the issue, if you wish to do so.