Unable to Add a Tape Robotic Library to Media Server

[rupadeviy]

Hi All,

we are trying to readd tapelibrary using device configuration wizard, it is showing detecting.

when we try to add robot manually,we are getting below error.

we can able to see robot at os level,below are the outputs of scan and tpautoconf

tpautoconf output :

# tpautoconf -r
TPAC60 HP MSL6480 5.10 DECxxxxxxxx -1 -1 -1 -1 /dev/sg646 -

#scan -changer

************************************************************
------------------------------------------------------------
Device Name : "/dev/sg646"
Passthru Name: "/dev/sg646"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : "HP MSL6480 5.10"
Vendor ID : "HP "
Product ID : "MSL6480 "
Product Rev: "5.10"
Serial Number: "xxxxxxxxxxx"
WWN : ""
WWN Id Type : 0
Device Identifier: "HP MSL6480 xxxxxxxxxxx1"
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-5
Number of Drives : 6
Number of Slots : 110
Number of Media Access Ports: 10
Drive 1 Serial Number : "xxxxxxxxxxxx"
Drive 2 Serial Number : "xxxxxxxxxxxxx"
Drive 3 Serial Number : "xxxxxxxxxxx"
Drive 4 Serial Number :"xxxxxxxxxxx"
Drive 5 Serial Number : "xxxxxxxxxx"
Drive 6 Serial Number : "xxxxxxxxxxx"
Flags : 0x0

when i try to add robot with tpconfig , iam getting below error

#tpconfig -add -robot 12 -robtype TLD -robpath /dev/sg646
Cannot add robot to device configuration: Incomplete robot information
Failed adding robot number 12 of type TLD to configuration.

[Marianne · Accepted solution]

Have you checked the following?

1. Device Compatibility list for 7.6:
   https://www.veritas.com/content/support/en_US/doc/NB_76_HCL
2. Updated Device Mappings:
   https://www.veritas.com/support/en_US/article.000025759
   (Not sure if the latest version will work with NBU 7.6)
3. Correct license keys:
   Enterprise Server and Library Based tape drive
4. Comms between master and media server
   Can you config and use disk STU as a test? 

*** EDIT ***

I just had a look at your error message in the Status Code manual :

Message: Incomplete robot information
Explanation: On a request to change the device configuration, some of the required
robot information was not specified.
Recommended Action: Check the command usage and reissue the request with
all required robot information specified.

Looking at tpconfig command reference: https://www.veritas.com/support/en_US/doc/123533878-127136857-0/v123555474-127136857
-robtype robtype

Robot type can be any of the following for NetBackup server:
tl4 for tape library 4mm
tl8 for tape library 8mm
tld for tape library DLT

Note that 'tld' is lowercase.
Please try that after you have checked everything else.

[rupadeviy]

i tried to run with tld in lowercase, but still same issue

tpconfig -add -robot 12 -robtype tld -robpath /dev/sg646
Cannot add robot to device configuration: Incomplete robot information
Failed adding robot number 12 of type TLD to configuration.

[mph999]

What happens if you add it using the wizard, all the way to the end, does it work ?  Just because the wizard can see it, doesn;t mean it will add successfully.

Another option is tpconfig (run just tpconfig) - this gives a txt menu, you can try and add in here.

If one of hopefully both the above work, we can they work out the command line version.  The reason I suggest this approach, is that if the robot doesn't add via the GUI (easiest way) it would suggest something else is wrong, and thus the command line will never work.

Can't say i've seen that error before, and as always with NBU (sadly) what the error looks like it may be, it could be completly mis-leading hence why it's important to determine if this 'can' work.

[Marianne · Accepted solution]

Have you had a look the 4 points in my previous post?

Can you confirm that comms is working fine between master and media server?

What do these commands show w.r.t this media server?
nbemmcmd -get_emmserver
nbemmcmd -listhosts -verbose

[Marianne]

@rupadeviy

Thanks for marking solution.
Can you please tell us how exactly you fixed the issue?

[rupadeviy]

Hi Marianne,

robot number was the issue, we added robot number 24 then it worked.

we have some unused libraries in our environment to which robot number 22 is assigned.

one quick query , we have robotic path zoned to 3 media servers, when i run device configured wizard , robotic path is getting changed from one media server to another media server

[Marianne]

Always best to use device config wizard from the master server, as it will automatically select the next unused number.
I always run device config and select only the media server that should be the robot control host followed be restart of daemons.
Then run device config wizard again, select robot control host plus other relevant media servers.

I don't think there is a way to select robot control host in the wizard.