Robotic Inventory error unable to sense robotic device (202)

[Mohd_Suhail]

I have an error when I try to do an inventory, it pops with the following error " Inventory failed: unable to sense robotic device (202)".

I am running Windows 2003 as a host and as a media server. It is connected to Dell PV136T which has 4 LTO2 drives.

I see on the device manager all is running okay, the medium changer and the tape drives.

I then check the event viewer in the application log where is see the following messages

Event Type:Error
Event Source:NetBackup TLD Control Daemon
Event Category:None
Event ID:14032
Date:5/8/2006
Time:9:01:22 AM
User:N/A
Computer:DUBIUTIL3
Description:
TLD(0) cannot open \\.\Changer0, SCSI coordinates {4,0,0,0}: The requested resource is in use.




Event Type:Error
Event Source:NetBackup TLD Daemon
Event Category:None
Event ID:5691
Date:5/8/2006
Time:9:01:22 AM
User:N/A
Computer:DUBIUTIL3
Description:
TLD(0) unavailable: initialization failed: Unable to open robotic path


Please someone help me out on this.

Thanks

[Deepak_Bhalwank]

Hi,

Which version of NetBackup you are using?

For NBU 6.0 following are requirements
PowerVault 136T DELL^^^^PV-136T SCSI ID TLD (3.03, 3.35, 3.35.0001) - Firmware version.
confirm firmware.

Robotic Status Code: 202 Message: Unable to sense robotic device Explanation: An element of the robotic library device could not be sensed. The cause
could be any of the following.
◆
The SCSI commands mode sense, mode select, or read element status (of slot, drive, transport, i/e element) may have failed.
◆
A network API-controlled library inventory request may have failed.
****(NOT VALID HERE)
◆
The robotic daemon/process could not initialize a robotic database file.
Recommended Action:
1.
Check the configuration of the robot against the recommended configuration as indicated in the documentation for robot configuration.
2.
Check the health of the robotic device by using a robot test utility, then close the test utility when finished.
****(USE \volmgr\bin\robtest)
3.
Check for the existence and permissions of the temporary robotic database and the temporary database directory/folder, which is /usr/openv/volmgr/misc/robotic_db (UNIX) or install_path\Volmgr\misc\robotic_db (Windows). Create the directory/folder and adjust the permissions as needed so that the robotic daemon/process can create it or use it. Stop and restart ltid (the device daemon on UNIX or the NetBackup Device Manager service on Windows).

I am assuming that four drives and one robot are added properly else use \volmgr\bin\scan command.

Regards,
Deepak.

[Mohd_Suhail]

Hi Deepak,

First of all, I would like to thank you for taking time to answer my question. I am new to Netbackup, so don't know much how to troubleshoot.

I have
Netbackup 6.0
Dell firmware 3.35.0001
Dell Tape drive 53Y3.


I have 2 Adaptec ultra scsi 39160 cards installed on my server.
I have connected the four drives to four scsi ports on the two scsi cards i.e 2 drives on each scsi card.

After posting the message on the forum, I had shutdown my server and tape drive. Restarted them it then was working.

I have being have this issue interminnetly, all of a sudden after a continous run of 8 days or more, netbackup would stop working. And i would get this robotic error.

When I had use the bpdown and the bpup, this sort of event would generate. Since I do not know how to troubleshoot I then rebooted my server and tape drive.

Event Type:Information
Event Source:Application Error
Event Category:(100)
Event ID:1004
Date:5/8/2006
Time:8:49:55 AM
User:N/A
Computer:DUBIUTIL3
Description:
Reporting queued error: faulting application ltid.exe, version 6.0.2005.906, faulting module msvcr71.dll, version 7.10.3052.4, fault address 0x0000fedc.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6c 74 69 ure lti
0018: 64 2e 65 78 65 20 36 2e d.exe 6.
0020: 30 2e 32 30 30 35 2e 39 0.2005.9
0028: 30 36 20 69 6e 20 6d 73 06 in ms
0030: 76 63 72 37 31 2e 64 6c vcr71.dl
0038: 6c 20 37 2e 31 30 2e 33 l 7.10.3
0040: 30 35 32 2e 34 20 61 74 052.4 at
0048: 20 6f 66 66 73 65 74 20 offset
0050: 30 30 30 30 66 65 64 63 0000fedc


Thks & Rgds
Suhail

[Lance_Hoskins]

Sounds like there's a connection issue. It appears as if you're running Windows. Does your Media server see the library from the OS? If not, you'll want to correct that first then move onto trying to get it to work in NBU. Once you get the OS to see the library, then you can re-scan the devices and things should work smoothly.

One other thing to check if the OS already sees the library... When doing the inventory, make sure you're not emptying the load port first if indeed there are no tapes in there. I've seen an error similar to yours if you put a check next to "Empty load port prior to inventory" if there's no tapes in the load port.

Lance

[Deepak_Bhalwank]

Hi Suhail,
Welcome to this forum.

I guess you have to connect all drives serially using ports on the tape library and then finally a single scsi connection from tape library to the media server will do the job. This should give you 4 tape drives and 1 robot on using 'Configure Storage Unit' wizard.

Using \NetBackup\volmgr\bin\scan is command line for detecting all physical devices connected to the machine.

This should solve the problem if not.

Since in your case ltid.exe is creating problem may be the last option in the above list can be tried by you, the next time similar problem occurs.

The following link may be useful -
http://seer.support.veritas.com/docs/279268.htm

I am not an NetBackup expert just working for testing my knowledge and earning some points.
-:) .

[Mohd_Suhail]

Hi,

My problem has come back again.

When I do the scan, I get these reults

************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name : "Tape0"
Passthru Name: "Tape0"
Volume Header: ""
Port: 2; Bus: 0; Target: 3; LUN: 0
Inquiry : "IBM ULTRIUM-TD2 53Y3"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "53Y3"
Serial Number: "9111167722"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 9111167722"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape1"
Passthru Name: "Tape1"
Volume Header: ""
Port: 3; Bus: 0; Target: 4; LUN: 0
Inquiry : "IBM ULTRIUM-TD2 53Y3"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "53Y3"
Serial Number: "1110238018"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 1110238018"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Changer0"
Passthru Name: "Changer0"
Volume Header: ""
Port: 4; Bus: 0; Target: 0; LUN: 0
Inquiry : "DELL PV-136T 3.35"
Vendor ID : "DELL "
Product ID : "PV-136T "
Product Rev: "3.35"
Serial Number: "DELL134051O4007"
WWN : ""
WWN Id Type : 0
Device Identifier: ""
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-2
Number of Drives : 4
Number of Slots : 42
Number of Media Access Ports: 12
Drive 1 Serial Number : "1110245380"
Drive 2 Serial Number : "1110237963"
Drive 3 Serial Number : "9111167722"
Drive 4 Serial Number : "1110238018"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape2"
Passthru Name: "Tape2"
Volume Header: ""
Port: 4; Bus: 0; Target: 1; LUN: 0
Inquiry : "IBM ULTRIUM-TD2 53Y3"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "53Y3"
Serial Number: "1110245380"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 1110245380"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 5; Bus: 0; Target: 2; LUN: 0
Inquiry : "IBM ULTRIUM-TD2 53Y3"
Vendor ID : "IBM "
Product ID : "ULTRIUM-TD2 "
Product Rev: "53Y3"
Serial Number: "1110237963"
WWN : ""
WWN Id Type : 0
Device Identifier: "IBM ULTRIUM-TD2 1110237963"
Device Type : SDT_TAPE
NetBackup Drive Type: 10
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0


After this I bpdown the services and then bpup, I see the following 2 errors in the event viewer

Event Type:Error
Event Source:NetBackup TLD Control Daemon
Event Category:None
Event ID:14032
Date:5/24/2006
Time:6:51:51 PM
User:N/A
Computer:DUBIUTIL3
Description:
TLD(0) cannot open \\.\Changer0, SCSI coordinates {4,0,0,0}: The requested resource is in use.


Event Type:Error
Event Source:NetBackup TLD Daemon
Event Category:None
Event ID:5691
Date:5/24/2006
Time:6:51:51 PM
User:N/A
Computer:DUBIUTIL3
Description:
TLD(0) unavailable: initialization failed: Unable to open robotic path



Please help me at what should I do next for this problem.

Thanks
Suhail

[Deepak_Bhalwank]

Hi,
This errors seem to be different from the first one. Initially ltid.exe was causing problems while now problem is with tldcd and tldd.
May be you can try trouble shooting for error 201 'Cannot acces device path' as in guide. Enabling MM logs by creating folders as in
install_path\Volmgr\debug\daemon
install_path\Volmgr\debug\ltid
install_path\Volmgr\debug\robots may help.
The scan output looks ok to me. Not sure of the drive sequence.

Br,
Deepak.

[Mohd_Suhail]

Thanks Deepak for replying.

I just could not wait any longer, so I had to do the usuall reboot the server and library.

When this thing happens again, which I am sure it will, I shall follow your troubleshooting steps. From where do I enable the MM logging.

Thanks
Suhail

[Lance_Hoskins]

Are you sure that the OS can sense and work with the library when this happens? Have you tried donig a robtest just to ensure functionality from the server to the library (leaving NBU out of the equation)? Next time it happens, give that a try first to narrow down the problem to being NBU related or not NBU related.

Lance

[Deepak_Bhalwank]

MM logs are enabled when we create above directories.
Putting VERBOSE=5 in ../volmgr/vm.conf increases debug info in Event Log messages.

The point is you will have to do trial and error, like checking library using robtest, monitoring if the problem occurs after some specific event (like loading tape in particular drive), trying suggestions from Lance.
I do not know if this will work.

Regards,
Deepak.

[Raghava_Chary]

Robotic sense (202) is out of netbackup issue ... Nothing to do with Netbackup however external factors will cause this error.

I can give you a small example, in our environment the library has been logically partioned to 3 libraries and these 3 have been assigned to different products like HPDP, TSM and Netbackup.

When we insert tapes of TSM and try to check in from Netbackup it used to give the same error..

So it was confirmed that (202) error while performing inventory is out of Netbackup scope.

Even Veritas did not help on this as they did not have any answer with them.

Raghava.

[zippy]

Mohd,

Raghava Chary is correct, give him 5, anyhow your problem is hardware related.

Check syslog for hardware related errors.
HBA
SCSI
fibre scsi router
library

Is the library door open?

JD