Hi , I am getting the following error in solaris [Master Server] while executing the robtest Robot Selection --------------- 1) TLD 0 2) none/quit Enter choice: 1 Robot selected: TLD(0) robotic path = /dev/sg/c0tw500104f000ba2b3el0 Invoking robotic test utility: /usr/openv/volmgr/bin/tldtest -rn 0 -r /dev/sg/c0tw500104f000ba2b3el0 Opening /dev/sg/c0tw500104f000ba2b3el0 robotic path /dev/sg/c0tw500104f000ba2b3el0 does not existRobotic test utility /usr/openv/volmgr/bin/tldtest returned abnormal exit status (1). Can I go with reconfiguration of robot. Pls give your suggetions to resolve this Issue.

That didn't resolve the issue. tpautoconf -report_disc only reports devices that may be missing, it doesn't fix anythingi. The issue I think resolved itself - the scsi_command I said to run, showed connectivity, that was before you ran the report_disc command. I think you had a 'intermittant' connectivity issue - whislt you were posting here, it 'disappeared' so when you ran some commands and found it worked, you think the commands fixed the issue, but as mentioned, -report_disc cannot fix anything, it reports only. Martin

Robotic path does not exist

Marianne
Level 6
13 years ago
Seems OS has lost connectivity to robot?

Check /var/adm/messages for errors.

Please post output of sgscan.
muhanad_daher
Level 6
13 years ago
try this :

/usr/openv/volmgr/bin/tpautoconfig -report_disc;

/usr/openv/volmgr/bin/sgscan -all

admincmd/nbrbutil -resetall;
mubarack_s
Level 6
13 years ago
Hi,

Pls fnd the below /var/adm/messages o/p and tpconfig. We are using SL500 tape library FYI.

May 16 13:36:43 SS93VPBK01 last message repeated 5 times
May 16 13:38:12 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
May 16 13:38:12 SS93VPBK01 last message repeated 1 time
May 16 13:38:12 SS93VPBK01 tldd[1397]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
May 16 13:38:29 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
May 16 13:40:14 SS93VPBK01 last message repeated 7 times
May 16 13:40:14 SS93VPBK01 tldd[1397]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
May 16 13:40:32 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
May 16 13:42:16 SS93VPBK01 last message repeated 7 times
May 16 13:42:16 SS93VPBK01 tldd[1397]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
May 16 13:42:34 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
May 16 13:42:49 SS93VPBK01 last message repeated 5 times
May 16 13:44:18 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
May 16 13:44:18 SS93VPBK01 last message repeated 1 time
May 16 13:44:18 SS93VPBK01 tldd[1397]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
May 16 13:44:36 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
May 16 13:46:20 SS93VPBK01 last message repeated 7 times
May 16 13:46:20 SS93VPBK01 tldd[1397]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
May 16 13:46:38 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
May 16 13:48:22 SS93VPBK01 last message repeated 7 times
May 16 13:48:22 SS93VPBK01 tldd[1397]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
May 16 13:48:40 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
May 16 13:50:24 SS93VPBK01 last message repeated 7 times
May 16 13:50:24 SS93VPBK01 tldd[1397]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
May 16 13:50:42 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
May 16 13:50:57 SS93VPBK01 last message repeated 5 times

root@SS93VPBK01 # tpconfig -d
Id DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   HP.ULTRIUM4-SCSI.000 hcart TLD(0) DRIVE=1
      /dev/rmt/1cbn                                                    UP
1   HP.ULTRIUM4-SCSI.001 hcart TLD(0) DRIVE=3
      /dev/rmt/0cbn                                                    UP
2   HP.ULTRIUM4-SCSI.002 hcart TLD(0) DRIVE=2
      /dev/rmt/2cbn                                                    UP
3   HP.ULTRIUM4-SCSI.003 hcart TLD(0) DRIVE=4
      /dev/rmt/3cbn                                                    UP

Currently defined robotics are:
TLD(0)     robotic path = /dev/sg/c0tw500104f000ba2b3el0

EMM Server = SS93VPBK01-01

Drives and Drives path are looks fine, But unable to connect the robot. Have checked the robot in SLconsole. Robot looks to be fine. I also suspect the connetivity between robot and OS. How can I test it?
revarooo
Level 6
13 years ago
According to the line in the messages below, you have lost connectivity to the robot.

Run: scan -changer

Do you see the robot? If not, probably a zoning issue, if you do, then delete the robot using tpconfig and re-add it using tpautoconf -a

May 16 13:50:24 SS93VPBK01 tldd[1397]: [ID 795118 daemon.error] TLD(0) unavailable: initialization failed: Unable to open robotic path
May 16 13:50:42 SS93VPBK01 tldcd[1429]: [ID 295976 daemon.error] TLD(0) [1429] robotic path /dev/sg/c0tw500104f000ba2b3el0 does not exist
mph999
Level 6
13 years ago
You don't really need to test it, it is not there :

/dev/sg/c0tw500104f000ba2b3el0 does not exist

robtest can't connect - that is a good enough test. But if you want to show with other commands:

/usr/openv/volmgr/bin/scsi_command -d /dev/sg/c0tw500104f000ba2b3el0

What does this command show ...

/usr/openv/volmgr/bin/scan (run from the robot control host):

And these two commands :

cfgadm -al

cfgadm -al -o show_FCP_dev

Regards,

Martin
Yasuhisa_Ishika
Level 6
13 years ago
Did you make some changes on this host?
SL500 replaced? FC cabling changed?

Please provide output of commands Muhanad wrote.
mubarack_s
Level 6
13 years ago
Hi,

Pls find the o/p

root@SS93VPBK01 # /usr/openv/volmgr/bin/scan -changer
************************************************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name : "/dev/sg/c0tw500104f000ba2b3el0"
Passthru Name: "/dev/sg/c0tw500104f000ba2b3el0"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "STK     SL500           1409"
Vendor ID : "STK     "
Product ID : "SL500           "
Product Rev: "1409"
Serial Number: "557000200809"
WWN          : ""
WWN Id Type : 0
Device Identifier: ""
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-5
Number of Drives : 4
Number of Slots : 141
Number of Media Access Ports: 15
Drive 1 Serial Number      : "HU19115358"
Drive 2 Serial Number      : "HU1911534Y"
Drive 3 Serial Number      : "HU19115354"
Drive 4 Serial Number      : "MXP1134E6T"
Flags : 0x0
Reason: 0x0

============

root@SS93VPBK01 # /usr/openv/volmgr/bin/scsi_command -d /dev/sg/c0tw500104f000ba2b3el0
Inquiry data: removable dev type 8h STK     SL500

====
#cfgadm -al -o show_FCP_dev
Ap_Id                          Type         Receptacle   Occupant     Condition
c2                             fc-fabric    connected    configured   unknown
c2::50060e80058ae905,0         unavailable connected    configured   failing
c2::50060e80058ae905,1         disk         connected    configured   unknown
c2::50060e80058ae905,3         disk         connected    configured   unknown
c2::50060e8006d44703,0         disk         connected    configured   unknown
c3                             fc-fabric    connected    configured   unknown
c3::500104f000ba2b3e,0         med-changer connected    configured   unknown
c3::500104f000ba2b48,0         tape         connected    configured   unknown
c3::500104f000ba2b4e,0         tape         connected    configured   unknown
c4                             fc-fabric    connected    configured   unknown
c4::50060e80058ae915,0         unavailable connected    configured   failing
c4::50060e80058ae915,1         disk         connected    configured   unknown
c4::50060e80058ae915,3         disk         connected    configured   unknown
c4::50060e8006d44713,0         disk         connected    configured   unknown
c5                             fc-fabric    connected    configured   unknown
c5::500104f000ba2b4b,0         tape         connected    configured   unknown
c5::500104f000ba2b51,0         tape         connected    configured   unknown

root@SS93VPBK01 # cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c0                             scsi-bus     connected    configured   unknown
c0::dsk/c0t0d0                 disk         connected    configured   unknown
c0::dsk/c0t1d0                 disk         connected    configured   unknown
c0::sg/c0t0l0                  unknown      connected    configured   unknown
c0::sg/c0t1l0                  unknown      connected    configured   unknown
c2                             fc-fabric    connected    configured   unknown
c2::50060e80058ae905           disk         connected    configured   unknown
c2::50060e8006d44703           disk         connected    configured   unknown
c3                             fc-fabric    connected    configured   unknown
c3::500104f000ba2b3e           med-changer connected    configured   unknown
c3::500104f000ba2b48           tape         connected    configured   unknown
c3::500104f000ba2b4e           tape         connected    configured   unknown
c4                             fc-fabric    connected    configured   unknown
c4::50060e80058ae915           disk         connected    configured   unknown
c4::50060e8006d44713           disk         connected    configured   unknown
c5                             fc-fabric    connected    configured   unknown
c5::500104f000ba2b4b           tape         connected    configured   unknown
c5::500104f000ba2b51           tape         connected    configured   unknown
sata0/0                        sata-port    empty        unconfigured ok
sata0/1                        sata-port    empty        unconfigured ok
sata0/2                        sata-port    empty        unconfigured ok
sata0/3                        sata-port    empty        unconfigured ok
sata0/4                        sata-port    empty        unconfigured ok
sata0/5                        sata-port    empty        unconfigured ok
usb0/1                         unknown      empty        unconfigured ok
usb0/2                         unknown      empty        unconfigured ok
usb1/1                         unknown      empty        unconfigured ok
usb1/2                         usb-device   connected    configured   ok
muhanad_daher
Level 6
13 years ago
c3::500104f000ba2b3e med-changer connected configured unknown
c3::500104f000ba2b48 tape connected configured unknown
c3::500104f000ba2b4e tape connected configured unknown

the library connected, try my above post and if you can use a GUI to configure storage device (define robots and device) and scan for master and all media servers.
mph999
Level 6
13 years ago
Odd - hasn't lost connectivity - it just responded ... Or if it did, it is back now ...

root@SS93VPBK01 # /usr/openv/volmgr/bin/scsi_command -d /dev/sg/c0tw500104f000ba2b3el0
Inquiry data: removable dev type 8h STK SL500

This command has just sent a 'scsi inquire' command stright to he library, ithe library answered with the response "removable dev type 8h STK SL500"

Try these :

/usr/openv/volmgr/bin/scsi_command -tur -f /dev/sg/c0tw500104f000ba2b3el0qq

/usr/openv/volmgr/bin/scsi_command -test -f /dev/sg/c0tw500104f000ba2b3el0qq

/usr/openv/volmgr/bin/scsi_command -send_diag -f /dev/sg/c0tw500104f000ba2b3el0qq

Martin
mubarack_s
Level 6
13 years ago
Hi All,

Thanks for your support. Issue has been resolved. I have run the tpautoconf -report_disc.

Now every thing seems to be fine. Thanks a lot.