robot inventory failed: unable to open robotic path (201)

[rianui]

Hi,

Last two days ago I did a PM on my ux boxes which included an MSL6000 tape library. When I try to do a backup it fails. So I did an ioscan but under H/W type I get NO_HW(file attached). I have tried installing the drive again under SAM but it says there is no tape drive found during scan. An inventory under Veritas also gives me "robot inventory failed: unable to open robotic path (201)". I have changed the fibre cable but still no response.
Kindly assist.

[Torsten.]

Did you already try to power cycle the library? Maybe the NSR is hung ... can you get network access to the NSR?

[rianui]

Yes I have already power-cycled abd the NSR in responding okay to a ping request.

Rianui

[Torsten.]

You say "I did a PM" - what exactly have you done?

[rianui]

I labeled all cables then removed them to do a preventive maintenance. After connecting all cables, all others servers were able to connect to an EVA and mount all drives ok.
However for this tape library, Veritas cannot run a backup. I have since removed the tape and SCSI card and resat them. Now when I run an ioscan (ioscan -fnC tape) the hash (#) prompt returns and no other message like before to indicate a NO_HW.
By the way, by NSR, I meant that the ethernet port is responding.


Rianui

[Torsten.]

"do a preventive maintenance" - what exactly have you done?

Do you have any zoning on your switches?

When you disconnected all the cables (why?) - did you connect them always to the same positions?

Did you already check the connection status between the NSR and the switch?

[rianui]

Hi Torsen,


Q: "do a preventive maintenance" - what exactly have you done?
A: I brought down the systems and blew dust from them including the library.

Q: Do you have any zoning on your switches?
A: No there are no zones defined.

Q: When you disconnected all the cables (why?) - did you connect them always to the same positions?
A: Yes I connected all cables to their previous ports. I had to move the machines from the server room so as not to blow dust into other existing systems.

Q: Did you already check the connection status between the NSR and the switch?
A: Yes I did...(is there a particular way of doing this?) I also used a different fibre cable to check this.

Currently, the library is responding again after when I run an ioscan commamd. The ux box shows it as claimed.
The problem now is to have it recognized by Veritas.

Rianui

[Torsten.]

Does it have another device file now?

If it has, then something has changed (different port ...).

[rianui]

Hi Torsten,

Thanks so much for your assistance. After the library was detected by the OS, a consultant from the company that installed Veritas came and sorted out Veritas. The backup software had lost the robot settings.
It is now working ok.
Thanks a lot.

Rianui

[rianui · Accepted solution]

the problem was caused by Veritas Netbackup losing the right driver for the robotic drive.
After the old driver was removed from the OS and installed afresh, communication resumed.