ADSM-L

Re: TSM, Solaris and Fibre connected drives ?

2004-04-15 13:45:21
Subject: Re: TSM, Solaris and Fibre connected drives ?
From: Luke Dahl <ldahl AT JPL.NASA DOT GOV>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 15 Apr 2004 10:44:46 -0700
Hi Farren,
    A quick update on our implementation.  We attached five 3590H1A drives to a
Sun 420R successfully in our 3494 library.  You must update all volumes to
readonly, delete your existing paths, possibly delete the drive entries (not
sure on that one) and setup a zone for your system hba and all of the ports
that contain the drives.
Our configuration is as follows:
One Emulex dual channel fiber card, with port 0 connected to switch 1 and port
1 connected to switch 2
Each drive is connected from port 0 to switch 1, and port 1 to switch 2

So, when we rebooted the system to create the new /dev/rmt entries we showed 20
*st entries.  Here's an example of what we see, you can see that Drive 1 has
four st entries (stepped by a value of five for each one):
DRIVE 1
Drive Name: DRIVE1
WWN: 50050763000072A8
Serial Number: 0000000CB518
7st -> ../../devices/[email protected],4000/[email protected]/[email protected]/[email protected],0:st

Drive Name: DRIVE6
WWN: 50050763000072A8
Serial Number: 0000000CB518
12st -> ../../devices/[email protected],4000/[email protected]/[email protected]/[email protected],0:st

Drive Name: DRIVE11
WWN: 50050763000072A8
Serial Number: 0000000CB518
24st -> ../../devices/[email protected],4000/[email protected]/[email protected]/[email protected],0:st

Drive Name: DRIVE16
WWN: 50050763000072A8
Serial Number: 0000000CB518
29st -> ../../devices/[email protected],4000/[email protected]/[email protected]/[email protected],0:st

 Essentially there were four *st entries for each drive, two for those going
through ports on switch 1, and two for ports on switch 2.  I called tech
support to find a way to determine how to setup for failover, but automatic
failover on the drives isn't support in Solaris.  So, we defined a drive for
each st entry (drive1 - 20) and defined a path for each entry.  We then were
able to see which drives were using the same ports by correlating the drive
serial number with each drive entry.  At that point, we offlined all but five
entries, keeping two over fiber channel path 0 and three over fiber channel
path 1 to utilize both switches (probably not necessary, but why not?).  If
you're only using one switch with a single channel hba I don't believe you'll
have any problems.  Let me know if you need any assistance or if this is
unclear at all.  Good luck!

Luke

Farren Minns wrote:

> Hi TSMers
>
> Running TSM 5.1.6.2 on a Sun E250 presently connected to 3494 lib with 2
> SCSI 3590 drives (H1A).
>
> I have a question for you.
>
> We will soon be changing the SCSI attached drives for fibre attached models
> (still going to be 3590 H1A in the 3494 lib) which will be connected to a
> Brocade switch. Now, I have very little experience with fibre drives and
> was wondering what the steps were both with Solaris (if anybody can help)
> and TSM. I am used to adding SCSI devices to Solaris and then using the
> /dev/rmt/??? format to define the drives to TSM, but I'm assuming this is
> total different with fibre drives. I am assuming that the World Wide Name
> convention will be used somewhere.
>
> Can anyone give me any advice or good documentation pointers etc.
>
> Many thanks in advance
>
> Farren Minns - John Wiley & Sons Ltd

<Prev in Thread] Current Thread [Next in Thread>