NDMP robot

[NBU35]

Hi

We have master server at solaris 10 and NBU 7.1, we have tape library i80, after reboot we its robot is not enabled.

Its configured on NDMP host.

this is what i got from robtest

 robtest
Configured robots with local control supporting test utilities:
  TLD(0)     robotic path = usnsh103:mc0

Robot Selection
---------------
  1)  TLD 0
  2)  none/quit
Enter choice: 1

Robot selected: TLD(0)   robotic path = usnsh103:mc0

Invoking robotic test utility:
/usr/openv/volmgr/bin/tldtest -rn 0 -r usnsh103:mc0

Opening usnsh103
mode_sense failed
sense key = 0x0, asc = 0x0, ascq = 0x0, NO ADDITIONAL SENSE INFORMATION
Enter tld commands (? returns help information)

Please suggest ..

Enable column is no on GUI.

[NBU35]

:/usr/openv# tpconfig -d
Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   HP.ULTRIUM5-SCSI.000 hcart2 Standalone
      /dev/rmt/0cbn                                                    UP
1   HP.ULTRIUM5-SCSI.001 hcart2 Standalone
      /dev/rmt/1cbn                                                    UP
2   HP.ULTRIUM4-SCSI.000 hcart3 Standalone
      nrst0a (usnsh103)                                                UP
3   HP.ULTRIUM4-SCSI.001 hcart3 Standalone
      nrst0a (usnsh102)                                                UP

Currently defined robotics are:
  TLD(0)     robotic path = mc0 (usnsh103 [SCSI b/t/l = 3/61/0] ),

After rebooting tape library again , tape drives become stand alone, earlier they were in AVR mode.

[Marianne]

How long do you wait for robot to become ready?

If you watch the robot during IPL, you will notice quite a number of steps before it goes to Ready state.

One of the steps during robot initialization is an inventory, where the robot scans each robot slot.

So, give robot enough time to start up before running any commands that need robot comms.

[NBU35 · Accepted solution]

Hi Issue is resolved, nDMP host was not able to see the robot , resetting the link of medium changer on ndmp host has resolved the issue, now robot is working perfectly well.