Greetings,
I have a solution to the problem of library sharing and
different rmt names.
We have a number of AIX TSM servers that all share the same tape
libraries, and at first it was a big aggrevation because frame1 drive 3
would be rmt3 on one server, and rmt5 on another server, and so on.
Anytime we needed to delete and rediscover a drive, it might come back
as a different logical name and we would have to update the path.
Eventually I got tired of it, and I wrote a script that runs against a
small table in a flat file, and renames the AIX device name so they are
the same on each system.
(our naming convention for the drives, ie. f1_d05, means frame 1, drive
5. You can use any convention you want of course.)
The table contains lines like:
rmt-name TSM-drive Path Serial Number
lto4_f1_d01 lto4_f1_d01 09-09 0007850942
lto4_f1_d02 lto4_f1_d02 09-09 0007850931
lto4_f1_d03 lto4_f1_d03 09-09 0007850943
lto4_f1_d04 lto4_f1_d04 0C-09 0007850935
lto4_f1_d05 lto4_f1_d05 0C-09 0007851058
lto4_f1_d06 lto4_f1_d06 0C-09 0007850928
That show the logical tape name the tape drive should have, the TSM
name, and the path and serial number. The script looks at each tape
drive on a system, and if its serial number appears in this table, it
checks to see if the logical name matches what is in the table. If it
doesn't, it uses the 'chdev' command to rename the device. So, when you
first do the discovery the drives might be:
root# lsdev -Cc tape
rmt0 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt3 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt4 Available 0D-09-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt5 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt6 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt7 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP)
And after you run the script the devices will be:
root# lsdev -Cc tape
lto4_f1_d01 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP)
lto4_f1_d02 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP)
lto4_f1_d03 Available 09-09-02 IBM 3580 Ultrium Tape Drive (FCP)
lto4_f1_d04 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP)
lto4_f1_d05 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP)
lto4_f1_d06 Available 0C-09-02 IBM 3580 Ultrium Tape Drive (FCP)
lto4_f1_d07 Available 0D-09-02 IBM 3580 Ultrium Tape Drive (FCP)
That way your path statements in TSM map the TSM device called
lto4_f1_d01 to AIX path /dev/lto4_f1_d01, and that remains true on every
AIX host.
This makes them a lot easier to maintain. Anytime we have to delete a
tape drive, we just rediscover the drive with cfmgmr, and then rerun our
script, and they get renamed back to the logical name they should be.
If anyone would like the script I would be happy to share it, but I
didn't know if it was acceptible practice to just post it to the whole
list.
Best Regards,
John D. Schneider
Phone: 314-364-3150
Cell: 314-750-8721
Email: John.Schneider AT Mercy DOT net
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Morris.Marshael
Sent: Tuesday, March 10, 2009 1:28 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM Library Manager
Thanks to all because of your emails you got me looking at how I created
the paths and this is where my problem was. I had the name reversed.
Once I changed this things started working.
Marshael
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Abid Ilias
Sent: Tuesday, March 10, 2009 1:39 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Library Manager
Also turn the SAN Discovery option ON, we have figured out that the only
way SAN Discovery would work was to run TSM as Root in UNIX. If you
have SAN Discovery option ON, it is supposed to fix any discrepancy.
I would make a spread sheet of all devices for library manager/client
and update the path definition on Library manager to reflect that. Here
is any example of one, in this case the rmt number match for Library
Manager and clinet. When you define a drive leave the default for
"serial" option and for the path definition use "autodetect=yes" which
is not default.
Drive Name Frame Row Element No Manager Client
DR5218 1 1 257 rmt7 rmt7
DR5167 1 2 258 6 6
DR5467 1 3 259 3 3
DR5457 1 4 260 0 0
DR5460 1 5 261 2 2
DR5475 1 6 262 5 5
DR5136 1 7 263 11 11
DR5304 1 8 264 12 12
DR5316 1 9 265 13 13
DR5335 1 10 266 14 14
DR5337 1 11 267 15 15
DR5338 1 12 268 16 16
DR0074 2 1 269 8 8
DR0053 2 2 270 9 9
DR0120 2 3 271 17 17
DR9931 2 4 272 18 18
DR0049 2 5 273 10 10
DR9995 2 6 274 19 19
DR5876 2 7 275 1 1
DR5956 2 8 276 4 4
DR5342 2 9 277 20 20
DR5846 2 10 278 21 21
Thanks
Abid Ilias
TSM Administrator
Networking Services and Information Technology
The University of Chicago
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David E Ehresman
Sent: Tuesday, March 10, 2009 12:23 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM Library Manager
Are you comparing the element number/serial number on each rmt device on
the client with the path definition for the client on the library
manager. rmt2 on the manager is not necessarily the same as rmt2 on the
client and the path statements on the library manager have to resolve
any differences.
David
>>> "Morris.Marshael" <Morris.Marshael AT MCCG DOT ORG> 3/10/2009 1:11 PM >>>
I checked the drives to see what element numbers they were pointing to
and checked the library to see what element they were showing for the
drives, all are in sync.
Thanks,
Marshael
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Kelly Lipp
Sent: Tuesday, March 10, 2009 1:04 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Library Manager
I've seen something similar in the non sharing environment if the
element number to drive relationship is whacked. For instance, you
suggest that the drive at /rmt0 is element 256 when in reality it's 257.
The library is instructed to mount a tape in element 256 and then TSM
looks for tape in /rmt0.
Verify that the paths and element numbers actually line-up correctly.
Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777 x7105
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Morris.Marshael
Sent: Tuesday, March 10, 2009 10:24 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM Library Manager
I have setup a library manager in TSM.
This server is TSM 5.5.2
I am setting up a library client and it also has TSM 5.5.2.
The TSM library manager is using the drives with no problem.
I have setup the paths for the library client and I'm having problems
with the client.
The server, when requested, will mount a tape from the client and change
ownership to the client name.
Within the client activity log I get:
ANR0408I Session 15 started for server LIBRARYSERVER (AIX-RS/6000)
(Tcp/Ip) for
library sharing.
ANR0409I Session 15 ended for server LIBRARYSERVER (AIX-RS/6000).
ANR8779E Unable to open drive rmt2, error number=2.
ANR0409I Session 3 ended for server LIBRARYSERVER (AIX-RS/6000).
ANR1404W Scratch volume mount request denied - mount failed.
Librarymanager tapes from AIX:
lsdev -Cc tape
rmt0 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt2 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt3 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt4 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt5 Available 07-08-02 IBM 3580 Ultrium Tape Drive (FCP)
smc0 Available 07-08-02 IBM 3584 Library Medium Changer (FCP)
client tapes from AIX:
lsdev -Cc tape
rmt0 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP)
rmt2 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP)
rmt3 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP)
rmt4 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP)
rmt5 Available 07-08-01 IBM 3580 Ultrium Tape Drive (FCP)
smc0 Available 07-08-01 IBM 3584 Library Medium Changer (FCP)
I have checked the serial numbers of the drives on the server to the
client and I believe that they are correct.
Can someone help me in figuring out what I have missed or what might be
the problem?
Thanks,
Marshael
mccg.org email firewall made the following annotation
************************************************************
CONFIDENTIALITY NOTICE:
The information transmitted in this e-mail message, including any
attachments,
is for the sole use of the intended recipient(s) or entity to which it
is addressed
and may contain confidential, privileged and/or proprietary information.
Any unauthorized
review, retransmission, use, disclosure, dissemination or other use
of,or taking any
action in reliance upon this information by persons or entities other
than the intended
recipient is prohibited. If you are not the intended recipient, you are
hereby notified
that any reading, dissemination, distribution, copying, or other use of
this message or
its attachments is strictly prohibited. If you have received this
message in error, please
notify the sender immediately by reply e-mail, or by calling (478)
633-7272, and destroy the
original message, attachments and all copies thereof on all computers
and in any other form.
Thank you. The Medical Center Of Central Georgia. http://www.mccg.org/
************************************************************
03/10/09, 12:24:19
This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR
OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the
use of the addressee(s) named above. If you are not the addressee, or the
person responsible for delivering this to the addressee(s), you are notified
that reading, copying or distributing this e-mail is prohibited. If you have
received this e-mail in error, please contact the sender immediately.
|
