TSM servers sees the drive as being defined and online along with the
library.
Can define a path for the library o.k. without any problems regarding it
staying online.
However as for the paths to the drives these have been  deleted and then
redefined and set to be online.
This is where the  problem arises as from this point the paths to the
drives stay active for maybe 30 seconds before going offline and setting
the drives themselves into a state of polling. This never used to happen
before and can't understand the inability to keep the paths online and
stable. Does anyone know why this kind of behaviour is exhibited ?



"CORP Rick Willmore" <RWillmore AT RSAC DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
27/09/2004 18:42
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: 3583 library problems






I use a scalar100 which is a 3583.  I dont believe this is a library issue
though .. rather a drive mapping issue.  Sounds like tsm isnt talking to
the drives.. ie.. sure you have the elements correct?  Has it ever worked?

R.