Emulex Storport driver resets my targets

Hi all,

I was using Emluex LP8000 (with Emulex mini port driver elxsli2.sys installed ) to connect to a JBOD that has 5 Targets (Target 5, 6, 7, 8, and 9; each Target has 1 Lun.)

When I upgraded the driver to Emulex Storport miniport driver, my Targets were reset to 0, 1, 2, 3, 4.

I have two questions:

1.) Can the target reset be prevented?

2.) I have a port upper filter driver loaded on all “SCSI/RAID Controllers”. What can I do, if anything, to prevent the targets reset?

Thanks

Peter Trinh

You could check with emulex support. There’s very likely little you can
do, but there might be some registry settings that you can use to
propagate the old target numbers across.

-p

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Trinh
Sent: Tuesday, August 10, 2004 5:01 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Emulex Storport driver resets my targets

Hi all,

I was using Emluex LP8000 (with Emulex mini port driver elxsli2.sys
installed ) to connect to a JBOD that has 5 Targets (Target 5, 6, 7, 8,
and 9; each Target has 1 Lun.)

When I upgraded the driver to Emulex Storport miniport driver, my
Targets were reset to 0, 1, 2, 3, 4.

I have two questions:

1.) Can the target reset be prevented?

2.) I have a port upper filter driver loaded on all “SCSI/RAID
Controllers”. What can I do, if anything, to prevent the targets reset?

Thanks

Peter Trinh


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

I’m guessing you don’t really mean reset, you are referring to target ID
mapping. That’s under control of the Emulex drivers. In the first case,
elxsli2 is the Emulex PORT driver, not a miniport. They do whatever they
do for target mapping - there are various options.

The Emulex miniport drivers (both SCSI and Stor) versions currently use
filter drivers to implement “persistent” binding and target/LUN mapping.
That’s the functionality you are looking for. We don’t recommend using
this because it’s counter to PnP - whatever your filter driver is doing,
it should do so in a manner that is not dependent on legacy SCSI device
numbering. Remember, these target numbers are just made up for Fibre
Channel - FC itself uses FCIDs when talking among nodes and those are
not exposed to Windows (nor are they guaranteed persistent). If you need
to do specific things for specific devices, you should use an identifier
associated with the device as recommended by SPC-2 or later, and various
other standards and committees. For example, use INQUIRY PAGE 83, Type 3
(or 2), with Lun associativity. This will allow your customers to move
devices around freely between controllers, etc.

You should also be using SetupDi calls instead of SCSI addresses in any
user-mode routines. The only devices that truly implement SCSI Target
IDs are parallel SCSI devices and these are in a terminal branch of the
storage evolutionary tree.

-----Original Message-----
From: Peter Wieland
Sent: Wednesday, August 11, 2004 10:31 AM
Subject: RE: Emulex Storport driver resets my targets

You could check with emulex support. There’s very likely little you can
do, but there might be some registry settings that you can use to
propagate the old target numbers across.

-p

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Peter Trinh
Sent: Tuesday, August 10, 2004 5:01 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Emulex Storport driver resets my targets

Hi all,

I was using Emluex LP8000 (with Emulex mini port driver elxsli2.sys
installed ) to connect to a JBOD that has 5 Targets (Target 5, 6, 7, 8,
and 9; each Target has 1 Lun.)

When I upgraded the driver to Emulex Storport miniport driver, my
Targets were reset to 0, 1, 2, 3, 4.

I have two questions:

1.) Can the target reset be prevented?

2.) I have a port upper filter driver loaded on all “SCSI/RAID
Controllers”. What can I do, if anything, to prevent the targets reset?

Thanks

Peter Trinh


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com