Thanks to you and to Mark for your replies. Unfortunately, I was not
explicit enough (again!) in my message.

Well, third time's the charm:

I need the drives to be recognized in a particular order. I've done this in
the past by tweaking lots of config files, and it was working until we added
some more drives. At that point everything went to heck, and as someone on
the list pointed out, cross-referenced drives can ruin your whole day.

Not having the time to mess with the config files, I fixed it by deleting
and manually recreating all 120 or so /dev/rmt links (for i in "" b bn c cb
cbn ....). Not terribly painful, but not terribly stable either. If I were
to delete /dev/rmt and do a devfsadm again, I know it'd mess me up.

I have some more hardware to add, and a three-day weekend coming up, so I'd
like to do it right. My documentation from the first experience is a little
hazy (trying to remember exactly what I did after a two-day high-stress
marathon), and I was hoping someone who had been through this might have a
clearer explanation of what files needed to be tweaked and how.

Thanks again for your patience, and thanks in advance for any assistance you
may be able to render.

-----Original Message-----
From: veritas-bu AT jasons DOT us [mailto:veritas-bu AT jasons DOT us]
Sent: Wednesday, January 08, 2003 4:44 PM
To: Donaldson, Mark
Cc: Shafto, Eric; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Procedure for creating /dev/rmt devices


On Wed, 8 Jan 2003, Donaldson, Mark wrote:

> If they're visible as targets then a simple reconfig reboot should handle
> it.  Either touch "/reconfigure" and reboot our "boot -r" from the BIOS
> prompt.

Similarly "reboot -- -r" (yes, you need all three dashes) will do the same
thing with a single command.

> You can check the drive visibility with "sgscan tape" beforehand or with a
> "probe-scsi-all" at the BIOS prompt.
>
> Yet another alternative is to run:
> "drvconfig && devlinks && disks && ports && tapes" as root on the cmd line
> and it'll emulate the reconfigure boot - although experience tells me that
> this sometimes locks up in high lun-count systems.

With Solaris 2.7 and later you can use "devfsadm" instead of the string of
commands listed above.  And as Mark mentioned it can lock or appear to
hang the machine if you have a large number LUNs but otherwise it should
be fine.  I've done this on systems with 10 SAN drive volumes mounted
without a problem.  Just have patience.  The command can take several
minutes to complete.

> Make sure to use persistent addressing in your SAN scheme - you don't want
> these addresses moving about.

I'll second that.  Cross-crossed drives can wreck your day.

-Jason

-----
Jason K. Schechner  -   check out www.cauce.org and help ban spam-mail.
=The difference between genius and stupidity is that genius has bounds.=
---There is no TRUTH.  There is no REALITY.  There is no CONSISTENCY.---
   ---There are no ABSOLUTE STATEMENTS   I'm very probably wrong.---


If you have received this e-mail in error or wish to read our e-mail disclaimer 
statement and monitoring policy, please refer to 
http://www.drkw.com/disc/email/ or contact the sender.