# 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?

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.

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

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
02-18-2014 03:42 PM
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

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

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.