I can answer that -- it was the cycling of TSM. We added 6 drives to our
3584 last year and I ran into the same issue. I could define the drives
but I got an error in defining the paths. As near as I can guess, TSM
gets the library configuration at startup -- number of slots and number
of drives anyway. And it doesn't seem to refresh until restart, OR until
you delete/define the library itself.
So your option 2 should have worked as well.
Tom Kauffman
NIBCO, Inc
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Rhodes
Sent: Friday, February 09, 2007 9:37 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Resolved: Adding drives to a 3584 library - ANR8978W on define
path cmd
I opened a case with IBM about this problem. Their reply was to
perform the first action listed below, and if that didn't work, do the
second.
1) Delete (rmdev) and rerecreate (cfgmgr) the SMC devices for the
library
robot. Then try to add the paths.
2) Deconstruct the ENTIRE library definition in TSM and recreate the
library.
I put this off until we had a scheduled outage last evening to put DST
patches
on AIX. This of course required us to take TSM down. While it was down
I deleted and recreated the SMC devices. Once TSM was brought
back up I was able create the drive and paths for the new tape drives.
Unfortunely, I don't know if the critical change that allowed me to
define
the
new drives and paths was the cycling of TSM (as per the actlog messages)
or
the delete/recreate of the robot devices (as per support).
Rick
----- Forwarded by Richard L. Rhodes/FirstEnergy on 02/09/2007 09:23 AM
-----
Richard L.
Rhodes/FirstEnerg
y
To
"ADSM: Dist Stor Manager"
02/02/2007 10:35 <ADSM-L AT VM.MARIST DOT EDU>
AM
cc
Subject
Adding drives to a 3584 library -
ANR8978W on define path cmd
(Document link: Richard L.
Rhodes)
We just added 2 additional tape drives to our 3584 library. We had 10,
now
we
have 12. I'm trying to define these drives to our library manager
instance. The
lib is up and running . . . live using the origional 10 drives. I added
the 2 new drives to the logical lib. In ISC I run the "add drive"
dialog,
plugging in the drive name I want and the rmt device. ISC then
reports an error, refering you to the actlog.
The actlog is below . . . .basically, it defined the drive, failed
on the define path, then deleted the drive. After the failed
define path cmd it issues msg ANR8978W indicating that I need
to restart my tsm server.
So, I assume you can not add a drive dynamically to a library. That's
ok,
but I'm confused with the restart. Should I restart asis (no new drives
defined, like ISC left it), or, manually define the drives and restart.
It also issues a ANR9999D msg. I'm assuming is just that the define
path
cmd failed.
Thanks
Rick
Here is what I found in the actlog . . .
02/02/07 10:09:36 ANR2017I Administrator 14579 issued command:
DEFINE
DRIVE
3584GO 3584go-f01r0c SERIAL=AUTODETECT
CLEANFREQUENCY=NO
NE (SESSION: 52588)
02/02/07 10:09:36 ANR8404I Drive 3584GO-F01R0C defined in library
3584GO.(SESSION: 52588)
02/02/07 10:09:36 ANR2017I Administrator 14579 issued command:
DEFINE
PATH
TSMLM1 3584go-f01r0c SRCTYPE=SERVER
DESTTYPE=DRIVE
LIBRARY=3584GO DEVICE=/dev/rmt157 (SESSION:
52588)
02/02/07 10:09:36 ANR8978W The number of drives in library 3584GO
has
been
increated from to Please restart the TSM server
to
update the configuration;(SESSION: 52588)
02/02/07 10:09:36 ANR1750E The server detected an internal error,
return
code = 272.(SESSION: 52588)
02/02/07 10:09:36 ANR9999D ThreadId<13> issued message 1750 from:
<-0x000000010001bfdc outTextf
<-0x0000000100785168
AdmDefinePath <-0x00000001001e9e58
AdmCommandLocal
<-0x00000001001ead98 admCommand
<-0x0000000100507694
SmAdminCommandThread <-0x000000010000e9dc
StartThread
<-0x09000000004942f8 _pthread_body (SESSION:
52588)
02/02/07 10:09:36 ANR2017I Administrator 14579 issued command:
DELETE
DRIVE
3584GO 3584go-f01r0c (SESSION: 52588)
02/02/07 10:09:36 ANR8412I Drive 3584GO-F01R0C deleted from library
3584GO.(SESSION: 52588)
-----------------------------------------
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.
CONFIDENTIALITY NOTICE: This email and any attachments are for the
exclusive and confidential use of the intended recipient. If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return email and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.
|
