Gianluca,

unfortunately IBM LTO drives *have* to be installed and used through IBM 
SSG drivers not by using adsmscsi.sys driver. Thus for FC-attached 3583 
the best you can do is what John already have done - use changer through 
TSM-driver and drives through Windows (RSM) driver.
I would be more than happy if opposite was true because there will be no 
room for Tivoli Flash 2.

Zlatko Krastev
IT Consultant

P.S. I've tried to sqeeze this to happen in a "unsupported" configuration 
for a customer three weeks ago but desperately failed. No chance to deal 
with drives through adsmscsi.sys.

Zlatko




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc: 

Subject:        Re: 3583 with SDG, Windows 2000 and Qlogic 2200 adapters

Hi all,

the problem rises from what happens expecially in W-2K environment.
Generally speaking :

1. The HBA maps the WWNs of the fibre devices presented by the fabric to
the SCSI addresses that OS understands: in W-2K environments with Q-Logic
HBAs there is also an intermediate step of mapping WWNs to Loop-ID (by 
HBA)
then to SCSI addresses known by the OS;
      WWNs(Fiber attached devices)----------------> LoopID(Q-Logic HBAs)
------------------>SCSI Addresses (Host)

2. The ordering of the devices  comes from the sequence represented in the
Name Server Table of the switch: this sequence is the one used by the
QLogic HBAs in W-2K environments to assign Loop IDs;

3, When devices are added, removed , fail or are swapped form a port to
another of the switch, the existing assigned Loop ID and hence the SCSI
address, may change.  W-NT/2K gives \\.\Tapex names are given starting 
from
the lowest SCSI address first and then numbered in ascending order 
starting
from zero; this cause problems when the SCSI address change for any 
reason.

4. the IBM SAN Data GW determines the LUN address of the tape devices
(static SCSI ID to LUN mapping). It adds one more mapping level  to be
considered, but this could not be a problem because when powered up, the
devices are automatically mapped and this mapping will be retained; if
additional devices are added they go to the end without changing the
previous device mapping.

Unfortunately, as you reported, Qlogic doesn't support Persistent Binding
on W-2K environments so it is strongly reccomended to use an alternative
naming convention:

- use device alias name in the form of mtx.y.z.n for all tape devices: 
this
identifies a device explicitly by its SCSI Target ID (x), LUN (y), SCSI 
Bus
Number (z) and SCSI Port on the Host (n);

- this naming convention is used by default on W-2K environments by the 
TSM
supplied device driver (ADSMSCSI).

So try to use this naming convention and the TSM supplied device driver 
for
W-2K environments.

I hope this helps..............and good luck!!!









Cordiali saluti / Best regards

Gianluca Perilli



Gianluca Perilli
Tivoli Customer Support
Via Sciangai n° 53 - 00144 Roma (Italy)



  
                      rs6000   
                      <rs6000@BTINTERNE        To: ADSM-L AT VM.MARIST DOT EDU  
  
 
                      T.COM>                   cc:    
                      Sent by: "ADSM:          Subject:  3583 with SDG, 
Windows 2000 and Qlogic 2200 adapters 
                      Dist Stor   
                      Manager"   
                      <[email protected]   
                      .EDU>   
  
  
                      22/06/2002 16:42   
                      Please respond to   
                      "ADSM: Dist Stor   
                      Manager"   
  
  



Hi all

Here's the scenario:

TSM 4.2.1.15 Server on Win2K
3583 with San Data Gateway
2109 Switch

Implemented the solution only to be called back with the library not
responding to TSM. After a closer inspection I notice that the library has
now been renamed by Windows from lb2.1.0.5 to lb3.1.0.6.

So, how is this possible. There have been no hardware address changes made
and I made sure to name the libary and the drives independently of the
windows generic naming ie

lb2.1.0.5 was configured as LTOLIB
\\.\Tape0 was configured as DRIVE1
\\.\Tape1 was configured as DRIVE2

I have read in the Qlogic literature that persistent naming is not
supported which means the binding needs to happen elsewhere. I cant zone
the switch to tightly because I will be configuring SAN agents next and
that means all the SAN attached hosts need access to the library.

Has anyone one out there seen this happening in a SAN environment and how 
I
can make it go away?


Any help is much appreciated

Rgds
John