At 2/23/2004 03:08 PM, Skottie Miller wrote:
Geoff Hardin wrote:
So, my question is this: is it possible to work on a filer head while serving the data up from the cluster partner? My concern is that you are upsetting the FC-AL integrity because we'll have to unplug the FC-AL cables from the adapters on the head when we pull the motherboard tray out. Then, since the recommended course of action is to run diagnostics after reseating and/or replacing the DIMMs, could we run a small set of the diagnostics before plugging in the FC-AL cables? Maybe we could / should use the FC-AL reset function from the diagnostics menu to get the loops back to normal?
sure is. in fact, I use failover far more for maintenance and upgrades
Can you upgrade one side and bring it up running a different DOT version from it's partner? And then have it takeover the partner, then down the partner to upgrade it?
Thanks,
Kerry
than for protection from a head failing ;-)
once you do a failover and power off the "failed" head, pulling the FC cables should have no effect, since those loops are unused at that point.
leave the FC cables pulled, and run just the memory diagnostics.
Maybe we've just been too cautious with our data, but I'd like to hear from other toasters if this is possible, advisable, and safe before putting our data at risk.
YMMV, but we've never had a problem working on a filer head while its partner servered all the data for the cluster.
one caution: make sure your physical installation is such that you can do the mechanical work you need (open the mobo tray, pull cables, etc) without affecting the other filer or the power to the disk shelves.
-skottie
--
Scott Miller | Animation Technology work: skottie@dreamworks.com | Dreamworks Feature Animation life: skottie@pobox.com | http://skottie-di.net "Change is required. Growth is optional" -anon
================================================================ Margaret.K.Herschel@jpl.nasa.gov JPL Information Services Jet Propulsion Laboratory Phone 818.354.1111
DISCLAIMER: The personal and professional opinions presented herein are my own and do not, in any way, represent the opinion or policy of JPL.