ADSM-L

Re: STK Library L700 and ACSLS

2007-02-02 10:37:46
Subject: Re: STK Library L700 and ACSLS
From: Len Boyle <Len.Boyle AT SAS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 2 Feb 2007 10:37:22 -0500
Matthias, 

Those firmware level are very old. You can look at the following IBM URL to 
track the latest levels available to the public. 

http://www-1.ibm.com/support/docview.wss?rs=546&context=STCVQ6Z&dc=D420&uid=ssg1S4000043&loc=en_US&cs=utf-8&lang=en

This web page reports a LTO-1 level of 5AU1L1S or 5AU1L1F.
And for a LTO-2 67U1L2S or 67U1L2F. These were released in Jan 2006 and nov 
2006.  

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Matthias Feyerabend
Sent: Friday, February 02, 2007 9:24 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] STK Library L700 and ACSLS

Firmware on IBM LTO1 is 4561, on IBM LTO2 4770. This is the latest firmware 
version STK provided us, maybe there are newer versions now available. I will 
check that with STK.

I know that we really dont need ACSLS to have only TSM on the library, even 
with several servers.
Discussing the "Wait for rewind failed" problems with STK, one of them 
mentioned we should move to ACSLS, what means investment of money and time.
I have some vague glance of hope, some error recovery in ACSLS is better and  
will stop getting these errors. ???

Matthias

Richard Sims wrote:

> This thread is dwelling on ACSLS, but is that actually a problem 
> solution?  What if the problem is that the library/drive is failing to 
> wait long enough for the rewind of a high-capacity tape, and considers 
> it "stuck in the drive" because it's not out of there in the allotted 
> time?  That kind of thing is fixed by drive firmware.
> So, see if your firmware is up to date.
>
>    Richard Sims
>
> On Feb 2, 2007, at 7:09 AM, Matthias Feyerabend wrote:
>
>> Hello,
>>
>> to clarify:
>>
>> We are not yet using ACSLS, but considering to use it in future to 
>> overcome errors we get permanently , once twice  a week.
>> Our libraries are connected as SCSI libraries over the SAN with  TSM, 
>> one server is library manager, the other servers library clients.
>>
>> My question is, is there some hope or even own experience, that 
>> switching to ACSLS will overcome the errors we see at present ( FSC
>> x3e24 for example).
>>
>> Matthias
>>
>>
>> Ibán Bernaldo de Quirós y Márquez wrote:
>>
>>> Hello Matthias,
>>>
>>> I am doing something similar... I am installing 3 TSM servers that 
>>> shares an SL8500 with ACSLS with LTO 3 drives...
>>>
>>> I have define 3 library clients to 1 library manager sharing an 
>>> ACSLS library... how did you define an scsi library client to to an 
>>> ACSLS libray manager ¿?
>>> Could you describe more your environment ¿? How many Library 
>>> managers did you have ¿? and library clients ¿? Connections ¿?
>>>
>>> Regards,
>>> Ibán.
>>>
>>> Matthias Feyerabend escribió:
>>>
>>>> Hello,
>>>>
>>>> We are using two STK Libraries L700 attached to FC with IBM-LTO1 
>>>> and IBM-LTO2.
>>>> They are defined to TSM 5.3 Library Manager (Windows) and Library 
>>>> clients as scsi Libraries.
>>>>
>>>> They are used from several library clients in Windows and Linux.
>>>> Both libraries are heavily used and we are running more and more in 
>>>> error situations (errors like 3e24 in fsc log) where libraries and 
>>>> drives are no longer usable and only a full power cycle of the 
>>>> library helps.
>>>>
>>>> Is there some experience that STK ACSLS software will help to 
>>>> overcome this painfull errors ?
>>>>
>>>> As TSM has its own driver we dont really need ACSLS, but perhaps we 
>>>> get better reliability.
>>>>
>>>> Any expertise ?
>>>>
>>>> Thank you.
>>>>
>>>> Matthias Feyerabend
>>>>
>>>>
>>>>
>>>> --
>>>> -- 
>>>> Matthias Feyerabend            | M.Feyerabend AT gsi DOT de
>>>> Gesellschaft fuer Schwerionenforschung    | phone +49-6159-71-2519
>>>> Planckstr. 1                | privat +49-6151-718781
>>>> D-64291 Darmstadt            | fax   +49-6159-71-2519
>>>>
>>>
>>
>>
>> --
>> -- 
>> Matthias Feyerabend            | M.Feyerabend AT gsi DOT de
>> Gesellschaft fuer Schwerionenforschung    | phone +49-6159-71-2519
>> Planckstr. 1                | privat +49-6151-718781
>> D-64291 Darmstadt            | fax   +49-6159-71-2519
>


-- 
--
Matthias Feyerabend                     | M.Feyerabend AT gsi DOT de
Gesellschaft fuer Schwerionenforschung  | phone +49-6159-71-2519
Planckstr. 1                            | privat +49-6151-718781
D-64291 Darmstadt                       | fax   +49-6159-71-2519

<Prev in Thread] Current Thread [Next in Thread>