Hi,
 
i have done this also and it succeded although not supported.
 
The worst thing i recognized was that after removing the shelf (before that we followed the same procedure as desribed by Daniel) that the filer (a FAS6070) was blinking orange on the front panel and reporting some kind of loop-error in the display.
 
This remained until the next reboot of the filer.
 
But as i understood Netapp-support this procedure can cause multiple errors e.g. a filer panic.
 
Rgds
 
Jochen
 

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Borders, Rich
Sent: Tuesday, October 16, 2007 2:31 AM
To: dleeds@edmunds.com; Andrew.George@anz.com; Fox, Adam; toasters@mathworks.com
Subject: Re: removing a loop from running filer

You eventy need to pull the enclosure services drives and make the loop unstable.

It is easy to test, but individual circumstances can come into play. That means a test and repro may not be sufficient and the ultimate answer is no support.




-----Original Message-----
From: Leeds, Daniel <dleeds@edmunds.com>
To: George, Andrew <Andrew.George@anz.com>; Fox, Adam; toasters@mathworks.com <toasters@mathworks.com>
Sent: Mon Oct 15 19:41:59 2007
Subject: RE: removing a loop from running filer


i got a suggestion to do a disk remove of all the spares on the loop first and then down the loop interface as well.

i realize this is not supported or recommended but this environment would take hours to bring down and back up and even for the 70 seconds or so it would take to reboot many apps are not graceful and would crash/corrupt because of this.

rock and a hard place, hours of downtime affecting numerous services may be the only safe way to go.  sigh.

--
Daniel Leeds
Manager, Storage Operations
Edmunds, Inc.
1620 26th Street, Suite 400 South
Santa Monica, CA 90404

310-309-4999 desk
310-430-0536 cell



-----Original Message-----
From: George, Andrew [mailto:Andrew.George@anz.com]
Sent: Mon 10/15/2007 4:37 PM
To: Fox, Adam; Leeds, Daniel; toasters@mathworks.com
Subject: RE: removing a loop from running filer

I've had mixed results and as Adam said, it's not supported.
If you absolutely have to I'd do a storage disable adapter before I
uncabled
(Oh and turn off Autosupport, you'll get a freaky number of cases
generated back at NetApp's if you don't)


  _____

From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]
On Behalf Of Fox, Adam
Sent: Tuesday, 16 October 2007 9:00 AM
To: Leeds, Daniel; toasters@mathworks.com
Subject: RE: removing a loop from running filer


I don't believe this is an official supported procedure.  There are
reports that it has worked, but there are others that
it has caused crashes.  I would wait until you can take a quick downtime
before doing this.


-- Adam Fox
adamfox@netapp.com



  _____

From: Leeds, Daniel [mailto:dleeds@edmunds.com]
Sent: Monday, October 15, 2007 4:26 PM
To: toasters@mathworks.com
Subject: removing a loop from running filer




I have not done this recently so I was hoping someone on the list has.
Basically I need to decomission a loop on an existing filer and migrate
the shelves to another filer.  I need to do this with the original filer
live and running no downtime can be incurred.

the aggregate has been destroyed
the disks were all zeroed and are now spares
i have verified each individual disk resides in the shelfs/loop i need
to remove and no data/root disks are in this loop

cluster failover will be disabled during this procedure.

at this point i should be able to remove the optical loop cabling and
the filer will complain but otherwise keep on running correct?

thanks for any input in advance

--
Daniel Leeds
Manager, Storage Operations
Edmunds, Inc.
1620 26th Street, Suite 400 South
Santa Monica, CA 90404

310-309-4999 desk
310-430-0536 cell





"This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential,  may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."