topic Re: Win2k3+Emulex LP10000DC connectivity issues in Windows Server 2003

Win2k3+Emulex LP10000DC connectivity issues

Terence Kumar — Mon, 25 Apr 2005 00:17:05 GMT

Hi
I have an ADIC Scalar i2000 zoned to my Proliant DL580/DL380 (Win2k3) on a separate HBA LP10000DC. I have this amazing problem where if i do a drive replacement or library reboot, the hosts will detect a disconnect from the tape devices, and a manual rescan will get them connected. However, Netbackup dies because the tape devices are no longer visible there (declared DOWN). Only a reboot of host solves this. I also know that there is a known issue with Windows2003/2000 and MS has a fix for it. See KB 873337.

My question is this though, does anyone know what the recommended settings for HBA when attached to Tape devices? I have the ones for storage (attached), but not for tape!

thanks in advance

Re: Win2k3+Emulex LP10000DC connectivity issues

Roger Faucher — Mon, 25 Apr 2005 05:53:33 GMT

Terence:

Is this your producthttp://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?pnameOID=371514&locale=en_US&taskId=135&prodSeriesId=371512&prodTypeId=12169&swEnvOID=1005

Even in the .pdf file you posted, there is no reference to LP10000DC so I assume HP renames the product when they OEM it.

Make a great day!

Roger

Re: Win2k3+Emulex LP10000DC connectivity issues

Terence Kumar — Mon, 25 Apr 2005 06:02:17 GMT

Hi Roger

The LP10000DC is purchased from Emulex. Its only certified for HP-UX/Tru64 so far i think. However, its sold by Emulex for use in Wintel platforms. So i guess it should be ok.

However, the tape drives get "lost" when anything affects the FC connectivity between drive and HBA.

tks

Re: Win2k3+Emulex LP10000DC connectivity issues

Roger Faucher — Mon, 25 Apr 2005 18:28:32 GMT

Terence:

New drivers and firmware here:

http://www.emulex.com/ts/index.html

Make a great day!

Roger

Re: Win2k3+Emulex LP10000DC connectivity issues

Terence Kumar — Mon, 25 Apr 2005 19:16:09 GMT

Roger,

Not the answer i needed. Thanks anyway.

terence

Re: Win2k3+Emulex LP10000DC connectivity issues

Marco Hogeveen_1 — Tue, 26 Apr 2005 00:47:28 GMT

Terence,

I think you need to configure persistent binding. This fixes a 'windows SCSI address' to a FC WorldWineName. In that case: no matter what happens on your SAN, the same WWN always gets the same SCSI Address.

You can configure it easily with the LPutil tool from Emulex. Use the default settings and see if it works.

Marco

Re: Win2k3+Emulex LP10000DC connectivity issues

Terence Kumar — Tue, 26 Apr 2005 04:28:40 GMT

Hi Marco

You are right about the "persistent binding". However, i still experience severe difficulties with my Netbackup recognising the drives again. The OS see's the drives OK though with a rescan. The only way to get the NEtbackup running again is a reboot.

terence

Re: Win2k3+Emulex LP10000DC connectivity issues

Stephen Kebbell — Tue, 26 Apr 2005 08:56:02 GMT

Hi,

You have probably already done this, but just check that you have disabled the Removable Storage Service. Not just set to Manual/stopped, but disabled.

Regards,
Stephen

Re: Win2k3+Emulex LP10000DC connectivity issues

Marco Hogeveen_1 — Wed, 27 Apr 2005 00:34:32 GMT

I'm not sure if Netbackup uses it's own device drivers? If it does, please make sure that the windows device drivers of the tape drive(s) and mediium changer are disabled in device manager. Also after a re-scan.

Re: Win2k3+Emulex LP10000DC connectivity issues

Terence Kumar — Thu, 28 Apr 2005 09:54:31 GMT

Hi Stephan

I had missed out the RSM disable portion of the hosts. Will do that soonest.

Hi Marco,

The drivers used are library vendors, not Netbackups.

Something that i forgot to mention though, i am seeing multiple paths to the medium changer in the library. How do i suppress this? Through windows registry or HBA parameters?

rgds
terence

Re: Win2k3+Emulex LP10000DC connectivity issues

Wilbur Lee Aymond Jr. — Fri, 09 Sep 2005 10:52:05 GMT

The problem with seeing multiple paths to the changer showed up once in an environment I was working in as well.

The solution was to change the persistent binding. i.e. I moved the medium changer's scsi id from 0 to 1, and all of the other devices moved up one number as well. This was actually a Solaris Legato Networker server and an HP 700e library, but the principle should be the same.

-might work for you too, I think it has something to do with the 0 scsi id being reserved on a few medium changers, but haven't been able to verify that yet.

If you are able to verify, let the group know.