How to reset mru robot whith no axp-vms server reboot ?

[Fodil ATTAR]

Hi,

Is it possible to reset mru robot whith no axp-vms server reboot ?
$ mru show robot
"ROBOT GKF0: is not responding: Operating system specific error.
%ROBOT-E-OS_ERROR, Operating system specific error"

Any hints will be very welcome.

Fodil.

[Karl Rohwedder]

Did you powercycle the robot?
Did you check the cabling/termination?

[Fodil ATTAR]

Hi Karl,

Yes we :
powercycled the robot.
Cables & termination have been changed yesterday by technician

Nota : an openvms mount command is successfully performed.
But any mru command fails.

We'd like to reset the GFK0 robot whithout rebooting....

Anyway thank's for your quick answer.

Danke, schuss.

Fodil.

[Ian Miller.]

Does the MRU INIT command work?
Where any other parts replaced or config changed - sounds like an issue communicating with the robot. Is the robot on the same or a different scsi bus than the tape drive(s)?

[Fodil ATTAR]

Hi Ian,

The mru init command give same error message
$mru init robot gkf0
ROBOT gkf0 is not responding: Operating system specific error.
%ROBOT-E-OS_ERROR, Operating system specific error

Other parts have been replaced by anacomp technician (robot scsi card & dlt8000 drive)

Yes the robot is on same bus as 2 drives.

For anacomp technician the way is "Just reboot the server"

Thank's for your Answer Ian.

Regards,
Fodil.

[Ian Miller.]

As a check of scsi connectivity try

$ MCR SYS$ETC:SCSI_INFO GKF0

If this fails to talk you could try
$ MCR SYSMAN IO AUTOCONFIG
which occationally will kick things into life otherwise I would suspect a scsi comms problem.

[Volker Halle]

Fodil,

you can turn on logging for MRU:

$ DEFINE MRU_LOG filename
$ DEFINE MRU_VERBOSE 1

maybe this helps to find out, what the problem may be. And then think about how it can be solved.

Reference:

http://www.hep.phy.cam.ac.uk/MRU/robot012_iguide_001.html

Volker.

[Fodil ATTAR]

Ian,

I tryied the command mc SYS$ETC:SCSI_INFO GKF0 unsuccessfully

same result for sysman io a/log

cheer's
Fodil.

[Fodil ATTAR]

Hi Volker,

I am trying...

Danke und schuss.

Fodil.

[Fodil ATTAR]

Hi,

The reboot of 1 of 4 (*) cluster member has been done unsuccessfully.
HP support's express an embarrassant silence.

So do we...

(*) Cluster of 2 Gs160 & 2 GS60
(mru concerned GS160)=> rebooted
(2GS60 + 1GS160) => not rebooted

Now I think about calling a marabout.

Any other idea ?

Fodil.

[Ian Miller.]

As SCSI_INFO and other commands fail to talk to the robot I suspect something is wrong with it or the communication patch to it and no rebooting VMS is going to get it fixed. hp field service need to get on site and fix it.

[Fodil ATTAR]

Hi,

The Snaky problem is solved, it was a pine in the internal scsi cabling chain of the ESL robot, which has been twisted, during the technician manipulation.

Obviously, the tests performed after the parts replacement didn't include a full cabling checking.

Thank's a lot to all.
Vielen Danke fur alles.

Fodil.

[Fodil ATTAR]

Cheer's