Automatic giveback commands

Contributors

In certain situations, you might need to manage your automatic giveback settings using ONTAP commands.

If you want to…​

Use this command…​

Enable automatic giveback so that giveback occurs as soon as the taken-over node boots, reaches the Waiting for Giveback state, and the Delay before Auto Giveback period has expired.

The default setting is true.

storage failover modify ‑node nodename ‑auto‑giveback true

Disable automatic giveback. The default setting is true.

Note: Setting this parameter to false does not disable automatic giveback after takeover on panic; automatic giveback after takeover on panic must be disabled by setting the ‑auto‑giveback‑after‑panic parameter to false.

storage failover modify ‑node nodename ‑auto‑giveback false

Disable automatic giveback after takeover on panic (this setting is enabled by default).

storage failover modify ‑node nodename ‑auto‑giveback‑after‑panic false

Delay automatic giveback for a specified number of seconds (the default is 600). This option determines the minimum time that a node remains in takeover before performing an automatic giveback.

storage failover modify ‑node nodename ‑delay‑seconds seconds

How variations of the storage failover modify command affect automatic giveback

The operation of automatic giveback depends on how you configure the parameters of the storage failover modify command.

The following table lists the storage failover modify command parameters that apply to takeover events not caused by a panic:

Parameter

Default setting

-auto-giveback true | false

true

-delay-seconds integer (seconds)

600

-onreboot true | false

true

The following table describes how combinations of the -onreboot and -auto-giveback parameters affect automatic giveback for takeover events not caused by a panic.

storage failover modify parameters used

Cause of takeover

Does automatic giveback occur?

-onreboot true

-auto-giveback true

reboot command

Yes

halt command, or power cycle operation issued from the Service Processor

Yes

-onreboot true

-auto-giveback false

reboot command

No

halt command, or power cycle operation issued from the Service Processor

No

-onreboot false

-auto-giveback true

reboot command

N/A
In this case, takeover does not occur

halt command, or power cycle operation issued from the Service Processor

Yes

-onreboot false

-auto-giveback false

reboot command

No

halt command, or power cycle operation issued from the Service Processor

No

Note The -auto-giveback parameter controls giveback after panic and all other automatic takovers. If the -onreboot parameter is set to true and a takeover occurs due to a reboot, then automatic giveback is always performed, regardless of whether the -auto-giveback parameter is set to true.

The -onreboot parameter applies to reboots and halt commands issued from ONTAP. When the -onreboot parameter is set to false, a takeover does not occur in the case of a node reboot. Therefore, automatic giveback cannot occur, regardless of whether the -auto-giveback parameter is set to true. A client disruption occurs.

The effects of automatic giveback parameter combinations that apply to panic situations.

The following table lists the storage failover modify command parameters that apply to panic situations:

Parameter

Default setting

-onpanic true | false

true

-auto-giveback-after-panic true | false

(Privilege: Advanced)

true

-auto-giveback true | false

true

The following table describes how parameter combinations of the storage failover modify command affect automatic giveback in panic situations.

Note Be aware that takeover can occur for other reasons in the event of a node panic. For example, if a node panics but the panic packet is not received by its partner, the partner might perform a heartbeat loss takeover. In this case, giveback would not be controlled by the -auto-giveback-after-panic parameter but would instead be controlled by the -onfailure parameter.

storage failover parameters used

Does automatic giveback occur after panic?

-onpanic true
-auto-giveback true
-auto-giveback-after-panic true

Yes

-onpanic true
-auto-giveback true
-auto-giveback-after-panic false

No

-onpanic true
-auto-giveback false
-auto-giveback-after-panic true

Yes

-onpanic true
-auto-giveback false
-auto-giveback-after-panic false

No

-onpanic false
If -onpanic is set to false, takeover/giveback does not occur, regardless of the value set for -auto-giveback or -auto-giveback-after-panic

No

Note

If you modify the default settings, the -onpanic parameter can override automatic giveback, as shown in the table above.

  • If the -onpanic parameter is set to true, automatic giveback is always performed if a panic occurs unless you have changed the default settings for the -auto-giveback and -auto-giveback-after-panic parameters. If both of these parameters are changed from their default (true) to false, then an automatic giveback will not occur after a panic, even if the -onpanic parameter is set to true.

  • If the -onpanic parameter is set to false, a takeover does not occur and clients experience a disruption in ONTAP data services. Therefore, automatic giveback cannot occur, even if the -auto-giveback-after-panic parameter is set to true.

Note
  • Takeover might occur for other reasons during node panic. In such cases, giveback is not controlled by the auto-giveback-after-panic setting.

  • If the -onpanic parameter is set to true, automatic giveback is always performed if a panic occurs unless you have changed the default settings for the -auto-giveback and -auto-giveback-after-panic parameters. If both of these parameters are changed from their default (true) to false, then an automatic giveback will not occur after a panic, even if the -onpanic parameter is set to true.

  • If the -onpanic parameter is set to false, takeover does not occur. Therefore, automatic giveback cannot occur, even if the -auto-giveback-after-panic parameter is set to true. A client disruption occurs.