Either method will work, but personally I would do a takeover/giveback during a maintenance windows, just to verify that the rc file changes are correct. Nothing worse than a typo causing a time-bomb.

I seem to recall somewhere that changing flow control settings may cause a momentary network outage, but I don’t have a reference for that. I’m sure the impact would be less than the pause you get during a takeover/giveback though.

HTH,
  Jeremy

On 8 Nov 2014, at 8:20 am, Philbert Rupkins <philbertrupkins@gmail.com> wrote:

Hello,

Anybody have experience setting Flow Control to none on an array (controllers) that are already being used in production?     We have a number of filers that were deployed with Flow Control set to Full on the 10GE interfaces.    NetApp best practices recommend setting Flow Control to none. 

Is it preferable to:

a)  Update the RC file with the Flow Control settings and do a takeover/giveback to apply the new flow control settings?

b)  Modify the interface Flow Control settings directly with the system up and running?    Then update the RC file so those settings will persist across future takeover/givebacks?  I know the interface would 'reset' and I'm not sure how long of an outage we can expect.

c)  Something else?

Our busiest ethernet based clients are VMWare ESXi hosts with pretty busy NFS datastores.

Thank you all in advance!   
Phil
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters

-- 
Jeremy Webber
Senior Systems Engineer
Animal Logic Pty Ltd
T: +61 2 8310 3577  <— please note changed number
M: +61 2 9383 4800
F: +61 2 9383 4801