Hello,
we had some trouble seeing the 3584 library when attached to a SAN. But I've
recognized in our configuration (lsdev -Cctape), that the LUN between drive
1 and drive 2 wasn't in use. Therefore I defined it manually into the "hole"
and it worked. By the way: You'll find the right device under TSM Tape
Drives.
Regards,
Joerg Nouvertne
http://home.wtal.de/the_swordsman
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Jeff Bach
> Sent: Montag, 10. September 2001 19:55
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Defining 3584 Library to TSM on AIX
>
>
> Yes. I have setup.
>
> From the OS, the library manager device will show up when the
> correct driver
> is loaded, cfgmgr is run, and ATL device 1 is visible through the SAN
> (fiber) from the system. We use Brocade between the server and
> tape drives.
>
> When I configured, 3584 was considered a SCSI device inside ADSM no matter
> what you are connected with.
>
> Device /dev/smc0 will show up when you can talk to the library.
>
> Atape level and fiber driver level are below:
>
> root@hoadsm4:/users/root $ lslpp -l| grep -i fib
> 4.3.3.50 COMMITTED Fibre Channel RAID Device
> root@hoadsm4:/users/root $ lslpp -l Atape.driver
> Fileset Level State Description
>
> ------------------------------------------------------------------
> ----------
> Path: /usr/lib/objrepos
> Atape.driver 6.1.4.0 COMMITTED IBM AIX Enhanced Tape and
> Medium Changer Device
> Driver
>
>
> Jeff Bach
> Home Office Open Systems Engineering
> Wal-Mart Stores, Inc.
>
> WAL-MART CONFIDENTIAL
>
>
> -----Original Message-----
> From: David Longo [SMTP:David.Longo AT HEALTH-FIRST DOT ORG]
> Sent: Monday, September 10, 2001 12:28 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Defining 3584 Library to TSM on AIX
>
> I have not done this yet, but - Have you installed the
> FC filesets
> on AIX
> that are required for support of FC? After doing this and
> connecting library
> and then run "cfgmgr" to have AIX pick up new device would be a
> few simple steps. (Probably need some FC config steps also).
>
> A quick thought to give you a start.
>
> David Longo
>
> >>> kleinr AT EXCHANGE.NIH DOT GOV 09/10/01 11:31AM >>>
> We are trying to set up TSM on an AIX system and are having
> problems
> getting TSM to see the 3584 library. I have done a search on the
> adsm-l
> archives and did not see anything about defining a 3584 to TSM.
>
> The AIX system is not seeing the 3584 tape library, when any
> commands that
> try to configure or look at the device is issued, an error is
> returned
>
> $ mkdev -l 'lb0'
> Method error (/etc/methods/cfgadsmdd):
> 0514-051 Device to be configured does not
> match the
> physical
> device at the specified connection location
> cfgadsmdd[valid]: the device is NOT supported
> cfgadsmdd[inq..]: free dds
> cfgadsmdd[main]: error inquiry or building dds, rc=51
>
> We need this device so we can continuing configuring the
> TSM server
> running
> on the system. Without configuring the tape library and
> drives, we
> can't
> configure TSM server.
>
> Part of the problem appears to be that the documenation does not
> describe
> the syntax for specifying a fiber channel device, which
> is the type
> of 3584
> library we have. It only mentions a SCSI device.
>
> Has anyone successfully defined a fiber channel 3584 to
> TSM running
> on AIX?
> Any help anyone can provide would be most appreciated.
> We have also
> submitted a problem ticket via our IBM support team, but have not
> heard
> anything back from them yet.
>
>
>
> "MMS <health-first.org>" made the following
> annotations on 09/10/01 13:34:41
>
> ------------------------------------------------------------------
> ----------
> --
> This message is for the named person's use only. It may contain
> confidential, proprietary, or legally privileged information. No
> confidentiality or privilege is waived or lost by any mistransmission. If
> you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it, and
> notify the
> sender. You must not, directly or indirectly, use, disclose, distribute,
> print, or copy any part of this message if you are not the intended
> recipient. Health First reserves the right to monitor all e-mail
> communications through its networks. Any views or opinions expressed in
> this message are solely those of the individual sender, except
> (1) where the
> message states such views or opinions are on behalf of a
> particular entity;
> and (2) the sender is authorized by the entity to give such views or
> opinions.
>
>
> ==================================================================
> ==========
> ==
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential
> and intended solely for the individual or entity to
> whom they are addressed. If you have received this email
> in error destroy it immediately.
> **********************************************************************
>
>
|
