ADSM-L

Re: [ADSM-L] show slots cmd

2007-06-22 09:11:06
Subject: Re: [ADSM-L] show slots cmd
From: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 22 Jun 2007 09:13:10 -0400
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 06/22/2007
09:00:41 AM:

> Life is a mystery...

Especially with tsm . . .

>
> What is the firmware level on each lib ?

both libs are 6830
all drives (3592) are 1949

> And the TSM Server level too.

TSM servers are all v5.3.3 . . . .I wonder if this is the issue, we are on
a older release.

> Have you compared the libvolumes (element adresses) and the Storewatch
list ?

Things seem to line up between TSM's view and the lib's view.  Actually,
we've had to
audit both lib's in the past day or so due to an inconsistancy due to a
tape problem.
We've just put in a monitoring script watching the tsm logs for msgs that
indicate
that a audit is needed.

Oh well, enough time spent.  I've got a old HP L700 (Omniback) that is
having
problems I've got to attend to.

Rick

>
>
> -----Message d'origine-----
> De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part 
> de
Richard Rhodes
> Envoyé : vendredi 22 juin 2007 14:34
> À : ADSM-L AT VM.MARIST DOT EDU
> Objet : Re: [ADSM-L] show slots cmd
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 06/22/2007
> 07:44:16 AM:
>
> > Because barcode are not recognized by the lib ?
>
> Also . . the 3584 lib web interface knows about the VolumeSerialNum in
each slot.
>
>
> -----------------------------------------
> 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>