Proliant 6400R SCSI Driver error!!! 1

[Burninator]

Hey Guys,

I have a client running two Compaq PL6400R servers in a cluster (Fiber Channel). Windows NT 4 SP6 Enterprise Server.

Connected to each of those servers is a Compaq TL891 Tape Library. On one of the servers the we are encountering a driver error "CPQ32FS2.dll parity error" on port 3 and sometimes port 4.

This seems to be affect the Tape library and Veritas Backup Exec from recognizing it as a changer or loader. I have run the latest Compaq Software Support Pack, which updated the drivers, and still we get that error in the event viewer.

We know the server controller sees the TL891 because at boot the SCSI controller lists it and its IDs correctly. Has anyone esle ever come across this problem?

Can anyone offer some suggestions or reccomendations? Compaq/HP of course won't help at all.

Thanks

 

[meireles]

That problem is typically caused by SCSI bus errors due to poor quality or malfunctioning cables or connectors. Also, you should check the electrical ground, and check if it's the same for both servers and tape lybrary; if it's not, you could be in trouble. Also, it could be that you're exceeding the allowed length of the SCSI bus (ie, a cable too long). Finally, it could be that the SCSI bus is not properly terminated.

Very high quality (but expensive) SCSI cables and connectors can be bought from Granite Digital on

http://www.granitedigital.com

They're no rookies - I remember hearing from them in the late eighties - and I already have bought from them more than once. To understand what I mean by "quality cables", some years ago (when Ultra SCSI was king and LVD didn't yet exist) I instaled some Granite Digital cables and terminators connecting a customer's Compaq servers to Compaq DLT drives on another room; they never had a glitch. According to the specification, the maximum allowed length for an Ultra SCSI bus is 1.5 meters; the cables were 20 meters long. That says it all.

Paulo Meireles

 

[Burninator]

Thanks Paulo,


Great information indeed, this confirms my thinking. We suspected the cables, we are working on it now to find out exactly which one it is!!!


Thanks again Paulo.