I have 36 drives.

It did happen on Linux and Windows. For sure you need to setup the
"Persistent Binding", especially for Qlogic HBA.

If you are using IBM LTO and Qlogic HBA, please checkout this link:
http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/tips0250.html

- Connection Option from 2 to 1
- Disable HBA Loop ID 

On 6/10/05, Sung Y Lee <sunglee AT us.ibm DOT com> wrote:
> I believe what you want is "persistent binding" setup for your HBAs.
> Depending on brands, but you should be able to get information on their
> website how to configure or setup.
> 
> I have observed this with AIX TSM server where rmts changed after the
> reboot.  I hope you don't have many tape drives.  I can't imagine changing
> or updating 20 or more drives.. yikes.
> 
> I guess you could go on vacation for more than 1 day and when you come back
> all problems will be resolved...hopefully.
> 
> Thanks,
> 
> Sung Y. Lee
> 
> 
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 06/10/2005
> 03:10:15 PM:
> 
> > Could use some help from any Windows gurus out there:
> > HOW do I keep Windows from changing the addresses of the TSM devices?
> >
> > This server is Win2K3 (but the same thing has occurred on Win2K),
> > TSM is 5.2.2.5.
> >
> > There are fibre connections from 2 HBA's to 2 different SAN switches.
> > 1 Fibre cable from each SAN switch to 1 LTO drive in a 3583 (that
> > way if we lose a switch, we can still access at least 1 drive).
> >
> > Yesterday in order to clean up a big tangle of fibre cables, the
> > Windows admin disconnected 1 fibre cable from the HBA, untangled
> > things and plugged the cable back into the HBA, EXACTLY the same
> > connection.  Repeat for the other cable.
> >
> > Windows RENUMBERED the library and tape drives  (For example, mt2.0.
> > 0.2 became mt1.0.0.2).
> > I saw the same thing once after a power outage, when the server came
> > up before the switch was powered up.
> >
> > Now, I know that to get TSM working again, all I have to do is
> > install the LTO drivers for these "new" devices, and update the TSM
> > path for each device.
> >
> > But I would really like to understand WHY this happens, and how we
> > can avoid it.  I would like to go on vacation one day, without
> > worrying that this should happen while I'm gone!
> >
> > Any insight appreciated!
> >
> > Wanda Prather
> > "* I/O, I/O, It's all about I/O *"  -(me)
> >
>