We've had some similar type problems, althought not that bad!
At times it's as through someone (aix, san, lib/drives) looses track of
things and starts fighting itself. It showed up as mount failures, reserve
conficts, and lib manager hanging. We never did figure out what happened
or why, but I believe it was AIX/TSM getting confused. The "solution"
that seemed to "work" was to completely dismantle the tape subsystem and
recreate it. By "dismantle" I mean completely blow it away: tsm
drives/paths, aix rmt/smc devices, fscsi/fcs adapters. And, not just drop
them to a defined state - delete them (clean out the ODM). Then, cfgmgr
it all back in, set your atape multi-pathing, define new drives/paths
toTSM. After doing this the problem finally went away. We've done this
enought that I put together some scripts to generate the TSM commands for
drive/path deletion and creation.
Rick
I would agree with this, but even further. We've had several instances
where problem where the "fix" that seemed to workwas to complete delete the
Nick Laflamme
<dplaflamme@GMAIL
.COM> To
Sent by: "ADSM: ADSM-L AT VM.MARIST DOT EDU
Dist Stor cc
Manager"
<[email protected] Subject
.EDU> Re: TS3500 PROBLEM
06/04/2010 12:15
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
Have you tried to verify that the devices your paths point to are still the
same? Or, better yet, deleted all your paths from all the library clients
and regenerated them from scratch?
We haven't run with a real 3584 in a while, but whenever I get weird errors
with library managers and shared libraries, that's where I go first. You
probably have, but you haven't said so, only that you've worked with the
SANDISCOVERY settings.
Just a thought,
Nick
On Jun 3, 2010, at 11:03 PM, Fred Johanson wrote:
> About 6 weeks ago, our hardware guy upgraded the code on the TS3500 and
ATape to the latest levels and made some hardware upgrades (details on
request). Within days we began to have assorted tape mount problems.
Supports initial response was to upgrade the TSM level to 5.5.4.2 to avoid
a known problem with SANDISCOVERY. So we upgrade to the latest V5R5 level,
but we still see problems. So we turn off SANDISCOVERY, and things get
quiet; the telltale AIX message "RESERVATION CONFLICT". Support asks us to
turn on SANDISCOVERY on various Library clients, with no effect until last
Friday, when the Library Manager goes crazy. So turn off SANDISCOVERY on
the LM and all goes quiet.
>
> Yesterday the CE upgraded the TS3500 to the very latest, and within
minutes the Library begins refusing to mount tapes, with total disregard to
the presence or absence of SANDISCOVERY and potentially disastrous effect
on LANFREE backups. As I see it, from my TSM seat, the common thread here
is the AIX message of "Reservation Conflict", which points to the hardware
changes made.
>
> So after hours of looking at logs and mount messages and traces, which
has left me groggy, the question is "Is anyone out there seen any
difficulty with the software combination of latest version of AIX 5, TSM
5.5, and the TS3500. Jeremiah, that's me, has been saying for weeks that
the problem lies somewhere in the combination of hba, switch, port, and
whatever, but management always blames TSM.
>
> Pardon my incoherence, but I've been reading logs, etc., for the lastin
15 hours.
-----------------------------------------
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.
|
