S/W State Says NO_HW

[Fern H2O]

Ok here's my problem,

We have a Overland NEO 8000 Tape Library and everything has been working fine untill two days ago when 4 drives went bad. So, Overland Techs came and replaced them. Drives are working good now but my Media Servers can't use them because the Device Files are not Claimed. I tried removing them and reinstalling the device file(rmsf & insf) but still it says NO_HW. Same problem with the Master server only that with the Master server I am able to reboot it but my media servers cannot have any down time. So when I rebooted the server everything worked out, the Devices were now CLAIMED.

Problem is I can't do that with the other servers because of No Down time. So, Does anyone know if theres another way I can resolve this issue??? It would be greatly appreciated.

THANKS!!!

[Torsten.]

Hi,

is the lib connected via fibre channel?

[Fern H2O]

Hello,

Yes, the Library is connect via fiber channel. And for some extra info the tape drives are: HP Ultrium 3-SCSI

[Torsten. · Accepted solution]

This sounds like a fiber chennal component was replaced too.
In this case the device has a new WWN, but comes with the same nport ID. The driver on your server doesn't allow the device to login.
Grep your syslog file for entries with "replace_dsk". If you find some, you need to tell the driver it is OK to allow the new device to log in:

fcmsutil /dev/td0 replace_dsk nport-ID

(replace /dev/td0 with the correct device, taken from your ioscan and nport-ID with the value from your syslog, e.g. 0x0111).

It's just a thought, because you mentioned it is working after a reboot.

[Fern H2O]

Hey Torsten, You seem to be right on point!

One question though, I'm not sure which device file to use. These are my options,

tape 2 1/10/0/0.100.2.255.1.3.0 stape NO_HW DEVICE HP Ultrium 3-SCSI
/dev/rmt/2m /dev/rmt/2mnb /dev/rmt/c26t3d0BESTn
/dev/rmt/2mb /dev/rmt/c26t3d0BEST /dev/rmt/c26t3d0BESTnb
/dev/rmt/2mn /dev/rmt/c26t3d0BESTb

Is there a specific one I should use??

[Torsten.]

You need the device file of the FC HBA, e.g. /dev/td0 or /dev/td1 ...

Search for the fc adapter on hw-path 1/10/0...

[Sandman!]

Try running ioscan without any arguments. This will force the binding of the device drivers to actual H/W found. After that see is the tape drive shows up as CLAIMED i.e.

# ioscan
# ioscan -funC tape

~cheers

[Fern H2O]

Torsten you were 100% Correct. Everything is now Claimed..

Thanks A LoT!!!

[Fern H2O]

Thanks!