>>1. The windows device manager always shows an exclamation mark next to
the SDG (Will not properly recognise it or configure it).

This is normal as long as you can see SCSI device attached to that SDG .


>>2. When trying to configure the drives and library into TSM, it will not
work using the Windows 2000 element addressing but rather the generic
addressing. This subsequently causes checkin libvol to fail (I think!)


1. Need to use adsm device driver "adsmscsi.sys" , go to service and make
sure adsm device driver started by system or before start dsmserver.

  ***TSM server do not support using generic device driver on SDG attached
device or local attached device on NTx ***

2. Need to use ADSM server utility to get the elements addressing, go to
device information to get the element addressing.



again, unload all windows device drivers and ONLY load SCSI device drive
for ALL devices(libraries) in San Data Gateway.

never use generic device driver come with windows or device FOR TSM
OPERATION UNLESS YOU ARE DOING "RESTORE local BACKUPSET FROM SDG"


Thanks and hope it help!! ^_^


Tivoli Storage Management Function Verification Test , FVT Automation
Project Lead
Office:408-256-3312 Home:650-757-1661 Cell:415-218-7880 AIM:smartbluewong
Dept Y0LA /Bldg 050-3 / Office 3A64
IBM SSG Division 46


John <rs6000 AT BTINTERNET DOT COM>@VM.MARIST.EDU> on 04/23/2002 11:55:00 AM

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:    3583 with San Data Gateway



TSM'ers I need help

I am trying to configure the above on an Xseries box running Win2K advanced
server. All the correct drivers have been used and all the components are
at the correct firmware levels.

All devices in the solution are connected to a 2109 S16

The problems I have encountered are as follows:

1. The windows device manager always shows an exclamation mark next to the
SDG (Will not properly recognise it or configure it).
2. When trying to configure the drives and library into TSM, it will not
work using the Windows 2000 element addressing but rather the generic
addressing. This subsequently causes checkin libvol to fail (I think!)

If any of you guys have ever configured something akin to this environment
you may be able to help me answer a couple of questions:

1. Based on the above, does anything immediately come to mind, from your
experience?
2. With the tape drives in the 3583 being SCSI but the attachment being
Fiber, must the TSM server "see" the drives as SCSI of fiber drives?

I know this may all sound rather vague but its the best way I could try and
explain it...

Help will be much appreciated.

Thanks
John