Personally, I do never enable auto giveback - most of the time, the filers have been taken over for a reason which needs to be investigated first before switching them back into production.

Just my 2 cents.

Alexander Griesser System-Administrator

ANEXIA Internetdienstleistungs GmbH

Telefon: +43-5-0556-320 Telefax: +43-5-0556-500

E-Mail: ag@anexia.atmailto:ag@anexia.at Web: http://www.anexia.athttp://www.anexia.at/

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

Von: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] Im Auftrag von Eric Peng Gesendet: Montag, 16. September 2013 21:37 An: toasters@teaparty.net Betreff: CF Giveback options

Am running ONTAP 8.1.2 P4..

Currently have the following settings enabled: cf.takeover.on_network_interface_failure on cf.takeover.on_network_interface_failure.policy any_nic

Want to enable setting: cf.giveback.auto.enable on

Was informed by IBM there is a bug where enabling auto CF giveback can conflict with cf.takeover.on_network_interface_failure, and result in the system getting into an infinite loop of takeovers and givebacks.

Do most of you leave auto CF giveback disabled as general policy?

Eric

I didn't turn it on specifically for this reason when I had one side in one network core and the other head in the other.   Now I have two ports per head crisscrossed into nexus 7000 cores.   The 7ks support channels across the cores (or something),  providing the redundancy we were looking for.

Meaning,  I still have never turned it on.

Sent from Yahoo! Mail on Android