This is from TSM L2 support....bottom line, restart TSM. No attempt to figure
out why I cannot define the drives/paths even though AIX sees the drives
through itdt.
=== SNIP ===
itdt -f /dev/smc0 inventory >inv.out
from inv.out, you can see all drives ( at beginning of the output ) which are
managed by /dev/smc0, if you don't see the drives from itdt then, there are no
way you are going to see that via tsm.
If you see the drives as expected in inv.out, then starts TSM or re-initiate
the TSM library, TSM should sync the library infor with device driver during
starts up, confirm the infor via command "show slots libraryname". If you see
the new drives via "show slots libraryname", then go ahead to define the
drive/path.
The SANdiscovery will only be triggered during tsm starts up and when the
device open failed ( with certain error) or when you run "q san ", Also, it
will only correct wrong device during discovery for drives TSM sees in your
defined library.
=== END ===
Had to get the servers in production, so just restarted TSM to continue with
the define.
Thanks for everyone's input.
Mahesh
________________________________________
From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Shawn
Drew [shawn.drew AT AMERICAS.BNPPARIBAS DOT COM]
Sent: Thursday, January 19, 2012 10:53
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Drive and Path Definition
The only other option to restarting the library manager is removing and
redefining all drives, library and paths. This would technically leave
the TSM server up and would still reprobe the library.
The Audit libr command never worked for me on a scsi library for these
updates.
Regards,
Shawn
________________________________________________
Shawn Drew
Internet
rrhodes AT FIRSTENERGYCORP DOT COM
Sent by: ADSM-L AT VM.MARIST DOT EDU
01/19/2012 09:57 AM
Please respond to
ADSM-L AT VM.MARIST DOT EDU
To
ADSM-L
cc
Subject
Re: [ADSM-L] Drive and Path Definition
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/19/2012
08:42:26 AM:
> > ...
> > Our libraries are 3584 scsi libraries, which are different animals
from
> > 3494 libraries. Sorry, I should have said that.
> >
> > Any time we have changed the physical library it has required us to
bounce
> > TSM so the new slots EA and/or drive EA are available to TSM. In our
> > case, that's our library manager tsm instance. We are still on v5.5,
but
> > I've seen nothing that would indicate that v6+ is any different.
>
> Rick -
>
> Have you tried Audit Library as part of the change procedure? It
> should perform a reconciliation with the reality of the library,
> using the same functionality that occurs when TSM restarts and
> checks the library.
>
> Richard Sims
This is interesting discussion.
Here's my story . . .
Our 3584 libraries started out witn 3 frames. They are now
at 8 frames. Sometimes a slot-only frame was added, other times
a frame with slots+drives. The first time we added a frame I
took the drives offline while IBM worked, but didn't bounce the
library manager. I loaded up the new frame with new tapes
assigned to the Logical Lib. Running checkin would not see the
new tapes. I also brought the new drives
in the new frame into AIX, created TSM drives, but failed on the
paths. Now, it was a long time ago
and I don't exactly remember, but I believe I did an audit
(but maybe I didn't). I also didn't know about "show slots" and
"show libr" cmds. I opened a case with support and was
told I needed to bounce the library manager. That worked, all was good.
Since then after making any physical change I bounce the library manager.
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.
This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Notice: The information and attachment(s) contained in this communication are
intended for the addressee only, and may be confidential and/or legally
privileged. If you have received this communication in error, please contact
the sender immediately, and delete this communication from any computer or
network system. Any interception, review, printing, copying, re-transmission,
dissemination, or other use of, or taking of any action upon this information
by persons or entities other than the intended recipient is strictly prohibited
by law and may subject them to criminal or civil liability. Carilion Clinic
shall not be liable for the improper and/or incomplete transmission of the
information contained in this communication or for any delay in its receipt.
|
