Lisa,
the problem is in the following:
tsm: TSM_HQ_1>define path tsm_hq_2 3494b srct=server destt=libr
devi=/dev/lmcp1
You should invoke this on TSM_HQ_2:
HQ_2> def libr
HQ_2> def path ... destt=libr
HQ_2> def path hq_2 drive1
HQ_2> def path hq_2 drive2
HQ_2> def path hq_2 driveN
!!!
HQ_1> def libr libt=shared
HQ_2> def path hq_1 drive1
HQ_2> def path hq_1 drive2
HQ_2> def path hq_1 driveN
You can define paths to library client before or after library definition
on the client. But the paths have to be defined on the library *manager*!
Library client contacts the manager, requests mount, receives back mount
request result with the drive path information, and accesses the volume
through that path
Zlatko Krastev
IT Consultant
Lisa Cabanas <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10.06.2003 17:37
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:3494 libraries on SAN-- how to define the clients??
Hi all ya'll,
I am beating my head against the wall, and was wondering if anyone had
been
down this road before?
Here are snippets of my PMR, with names removed to protect the innocent
> Problem Description:
> I cannot follow the directions to define a Library client in a SAN for
> a 3494 library.
> TSM_HQ_1 is the library manager for 3494A, which is defined as lmcp0 on
> the server (hostname scpm01). LMCP1 on this server is the SAN
> connection to the other 3494 library, which is managed by TSM_HQ_2 and
> is known as 3494B on the other server (hostname scpm02). On scpm02
> lmcp0 is 3494A and lmcp1 is 3494B. There are 4 fibre paths to each
> drive, so on each server there are 32 defined 3590 H drives, even
> though there are physically only 8 drives in each library.
> I am unable to define the path/library/drives, either getting the error
> messages that you can't do that for library type shared or the source
> is wrong or the path is unavailable.
> What is the proper sequence/ proper commands to define a 3494 library
> client on the SAN?
> When I had a PMR opened for me a while back (15823,999- I think?? Maybe
> 28393,999??) on TSM System Recovery & Backup, the person I talked to
> ( x?) knew what I was talking about and told me
how to
> do it. I wrote the steps down.but now I can't find my notes and I
> haven't been able to remember what the trick was..
>
> Lisa,
> There is a documentation flaw that was addressed in APARs IC34590 and
> IC34020:
> IC34590:
> ERROR DESCRIPTION:
> The Managed System for SAN Storage Agent User's Guide (for all
platforms)
> for TSM 5.1 mentions :
> Note: The DEFINE PATH command must be issued from the server (library
> manager or library client) that will manage the client's data.
> The above is an incorrect statement since the define path is not
supported
> on the library client (as indicated in apar IC34020). The define path
must
> be done on the library manager, which means that the following action
would
> need to take place :
> 1. define share libr in library client.
> 2. define storage agent in library client.
> 3. define path in library manager for library client to use
> the drive.
> 4. set crossdefine on in both library client and manager.
> 5. start storage agent to connect to library client.
> ( this will define this storage agent in the library manager with the
use
> of crossdefine)
> --or--
> manually define storage agent in library manager.
> 6. define path for storage agent in library manager.
> 7. re-start the storage agent to connect to library client.
> 8.start lan-free backup to library client
> .
> IC34020:
> Tivoli Storage Manager Administrator's Guide books for AIX, HP-UX,
Linux,
> Sun Solaris, and Windows operating systems will be updated to remove the
> incorrect steps in the procedure for setting up the library client.
> The correction will be made in both the procedure for setting up library
> sharing for a SCSI library and the procedure for setting up library
sharing
> for a 3494 library. Corrections will appear in books when the books are
> updated for the next release of the product(after Version 5.1.5)
> The correction is in the procedure for setting up the library client. In
> place of two steps that direct you to define the drives in the library
and
> define the path from the library client to each drive, you need to
perform
> the following step: Perform this step from the library manager. Define a
> path from the library client to each drive. The device name should
reflect
> the way the library client system sees the device. For example, if the
> library client is on a Linux operating system, issue the following
command:
> define path client drivea srctype=server desttype=drive
> library=3494san device =/dev/IBMtape0
>
> I guess I am just dense.
> I do
> tsm: TSM_HQ_1>define libr 3494b libt=shared primary=tsm_hq_2
> ANR8400I Library
