ADSM-L

Re: [ADSM-L] IBM 3584 preventive maintenance schedule

2010-04-08 22:50:38
Subject: Re: [ADSM-L] IBM 3584 preventive maintenance schedule
From: "John D. Schneider" <john.schneider AT COMPUTERCOACHINGCOMMUNITY DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 8 Apr 2010 19:49:34 -0700
You can always use tapeutil to load the drive or library firmware.  It
still has to be done one at a time, but is MUCH faster than the GUI
version; only a couple minutes per drive.  

Best Regards,

John D. Schneider
The Computer Coaching Community, LLC
Office: (314) 635-5424 / Toll Free: (866) 796-9226
Cell: (314) 750-8721

 
 
-------- Original Message --------
Subject: Re: [ADSM-L] IBM 3584 preventive maintenance schedule
From: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
Date: Thu, April 08, 2010 8:35 pm
To: ADSM-L AT VM.MARIST DOT EDU

> This can be tedious, however,
> because upgrading them all at once via the Web interface is about the
> speed of upgrading one.

We have had problems upgrading the drive microcode. When upgrading
all the drives at one time, the update proceeds and finally
ends with an error. THe state of the drives is such that some
have the new microcode and some do not. TO finish the update
we have then manually upgraded the remaining drives one at a
time - what a pain! THis has happened more than one, and IBM
has not resolved the problem. In talking with our local
CE, he said that the issue is that the rs422(?) bus connecting
the drives to the processors is overloaded during the upgrade,
and cuases timeout conditions.
We now let IBM perform the update, and he updates the drives
one frame at a time - something the gui doesn't support.

Rick

-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.

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