E3500 Internal Drive replacement

[Michael Sproelich]

There is a Sun infodoc on the procedure, 18595.  There are a few patches that
are required to make sure the luxadm commands work on the E3500.  On systems
without the patches I've had trouble, and had to futz with drvconfig and disks
after inserting the disk to get it to work, otherwise the luxadm insert works
great.  Note the added steps for VM, vxdiskadm option 11 to offline the disk. 
I've tested this procedure on E3500's and it seems to work well. 
Michael


Paul Hedgepeth wrote:
> 
> peter,
> 
> i have not had experience with your exact situation (never
> personally seen an E3500).  two of the situations i have
> encountered that would be similar to yours are as follows:
> replaced failed hard drives (hot-swapped) on A5000 arrays
> connected to an E4500 via a hub and added (not replaced)
> internal drives to a E250 (quasi hot-swapping, rather
> hot-adding).
> 
> your solution will probably require a combination of the two.
> your procedures seams a little overkill (then again some of mine
> are too).  for example, luxadm remove_device and insert_device
> actually cleans up/creates the physical and logical device nodes
> (at least when using for a drive in an A5000).  not exactly sure
> off the top of my head why your procedures didn't work.  will
> give it some thought in some "spare" time.
> 
> on an E250: the adding of internal hard drives, here are general
> procedures that i used:
> 1) inserted the drive into the slot
> 2) drvconfig; disks
> 3) vxdctl enable
> 4) initialize disk (use vxdisksetup, vxdiskadm #1 or the gui)
> 5) add to disk group (use vxdg or the gui)
> 6) create volumes (use vxassist or the gui)
> 
> on an A5000 array: see my attached procedures.
> 
> personally, i prefer using the command line starting at the disk
> initialization step so i can script these things out, monitor
> for a little bit and go home for the night (note: i've done this
> many times and feel confident and confortable enough on the
> scripts i write to actually leave - of course i'm also
> monitoring from home).  attached is a sample generic script that
> i base all my scripts on.  (are there easier ways to do this...
> probably so)
> 
> furthermore, in case of catastrophic failure or new system
> integration (ie: new arrays -or- new system and new arrays), you
> will have all of the above create scripts on backup tape to
> easily recreate your volume manager configuration!
> 
> if you have any questions feel free to contact me.
> 
> later,
> paul
> 
> =====
> Until our paths cross...
>      Be a turtle, take a chance and stick your head out.
>      Just don't be stupid about it.
> 
> Paul Hedgepeth
> hedge@alumni.nd.edu
> 
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com
> 
>   ------------------------------------------------------------------------------
>                           Name: vm_sample_script
>    vm_sample_script       Type: application/x-unknown
>                       Encoding: base64
>                    Description: vm_sample_script
> 
>                                      Name: Photon-disk-replacement.doc
>    Photon-disk-replacement.doc       Type: Microsoft Word Document (application/msword)
>                                  Encoding: base64
>                               Description: Photon-disk-replacement.doc

--