Re: Jaguar tape paths
- From: Soós Zoltán <soos.zoltan@xxxxxxxxx>
- Date: Tue, 23 Jan 2007 14:01:43 +0100
Bob,
A guy from adsm-l has suggested the use of tapeutil in this form: tapeutil
-f /dev/rmt0 path. It works like a charm. Just in case anyone else runs into
it.
Thanks,
sbzx
On 1/19/07, Bob Booth <booth@xxxxxxxx> wrote:
On Fri, Jan 19, 2007 at 08:04:41AM +0100, So?s Zolt?n wrote:
> Hi,
>
> I have a customer with a 3494 library and half a dozen of Jaguar tape
> drives, all of which are connected to two separate SANs. The host OS is
AIX
> and a multi-path driver is installed. All drives have a PRImary path and
an
> ALTernative path to the host OS. Does anyone know how to determine the
exact
> path used at any given time? PRI and ALT paths are assigned at setup
time
> and the location codes do not change when the PRI path is taken over by
the
> ALT path in case of a link error, so the location code is not helpful in
> determining the current path used. Also, "lsattr" and "lscfg" outputs do
not
> seem helpful.
>
> I am trying to find a command line method.
>
> Any help would be appreciated. Thanks.
What version of the OS is your customer using?
Have you used the 'lspath' command, so see what weights have been assigned
to the pri and alt paths?
You might also ask this question on the adsm-l list, as there are many
users
of AIX and 3592 tape tech there. They will probably ask the same
question,
so be prepared to describe your customers environment in your note.
cheers,
bob
- Follow-Ups:
- Re: Jaguar tape paths
- From: Bob Booth
- Re: Jaguar tape paths
- References:
- Jaguar tape paths
- From: Soós Zoltán
- Re: Jaguar tape paths
- From: Bob Booth
- Jaguar tape paths
- Prev by Date: Re: Volume Group issue
- Next by Date: Re: Jaguar tape paths
- Previous by thread: Re: Jaguar tape paths
- Next by thread: Re: Jaguar tape paths
- Index(es):