Description of node states displayed by storage failover show-type commands

You can use the storage failover show, storage failover show-takeover, and storage failover show-giveback commands to check the status of the HA pair and to troubleshoot issues.

The following table shows the node states that the storage failover show command displays:

State Meaning
Connected to partner_name. The HA interconnect is active and can transmit data to the partner node.
Connected to partner_name, Partial giveback. The HA interconnect is active and can transmit data to the partner node. The previous giveback to the partner node was a partial giveback, or is incomplete.
Connected to partner_name, Takeover of partner_name is not possible due to reason(s): reason1, reason2,.... The HA interconnect is active and can transmit data to the partner node, but takeover of the partner node is not possible.

A detailed list of reasons explaining why takeover is not possible is provided in the section following this table.

Connected to partner_name, Partial giveback, Takeover of partner_name is not possible due to reason(s): reason1, reason2,.... The HA interconnect is active and can transmit data to the partner node, but takeover of the partner node is not possible. The previous giveback to the partner was a partial giveback.
Connected to partner_name, Waiting for cluster applications to come online on the local node. The HA interconnect is active and can transmit data to the partner node and is waiting for cluster applications to come online.

This waiting period can last several minutes.

Waiting for partner_name, Takeover of partner_name is not possible due to reason(s): reason1, reason2,.... The local node cannot exchange information with the partner node over the HA interconnect. Reasons for takeover not being possible are displayed under reason1, reason2,…
Waiting for partner_name, Partial giveback, Takeover of partner_name is not possible due to reason(s): reason1, reason2,.... The local node cannot exchange information with the partner node over the HA interconnect. The previous giveback to the partner was a partial giveback. Reasons for takeover not being possible are displayed under reason1, reason2,…
Pending shutdown. The local node is shutting down. Takeover and giveback operations are disabled.
In takeover. The local node is in takeover state and automatic giveback is disabled.
In takeover, Auto giveback will be initiated in number of seconds seconds. The local node is in takeover state and automatic giveback will begin in number of seconds seconds.
In takeover, Auto giveback deferred. The local node is in takeover state and an automatic giveback attempt failed because the partner node was not in waiting for giveback state.
Giveback in progress, module module name. The local node is in the process of giveback to the partner node. Module module name is being given back.
  • Run the storage failover show-giveback command for more information.
Normal giveback not possible: partner missing file system disks. The partner node is missing some of its own file system disks.
Retrieving disk information. Wait a few minutes for the operation to complete, then try giveback. The partner and takeover nodes have not yet exchanged disk inventory information. This state clears automatically.
Connected to partner_name, Takeover is not possible: Local node missing partner disks After a takeover or giveback operation (or in the case of MetroCluster, a disaster recovery operation including switchover, healing, or switchback), you might see disk inventory mismatch messages.

If this is the case, you should wait at least five minutes for the condition to resolve before retrying the operation.

If the condition persists, investigate possible disk or cabling issues.

Connected to partner, Takeover is not possible: Storage failover mailbox disk state is invalid, Local node has encountered errors while reading the storage failover partner's mailbox disks. Local node missing partner disks After a takeover or giveback operation (or in the case of MetroCluster, a disaster recovery operation including switchover, healing, or switchback), you might see disk inventory mismatch messages.

If this is the case, you should wait at least five minutes for the condition to resolve before retrying the operation.

If the condition persists, investigate possible disk or cabling issues.

Previous giveback failed in module module name. Giveback to the partner node by the local node failed due to an issue in module name.
  • Run the storage failover show-giveback command for more information.
Previous giveback failed. Auto giveback disabled due to exceeding retry counts. Giveback to the partner node by the local node failed. Automatic giveback is disabled because of excessive retry attempts.
Takeover scheduled in seconds seconds. Takeover of the partner node by the local node is scheduled due to the partner node shutting down or an operator-initiated takeover from the local node. The takeover will be initiated within the specified number of seconds.
Takeover in progress, module module name. The local node is in the process of taking over the partner node. Module module name is being taken over.
Takeover in progress. The local node is in the process of taking over the partner node.
firmware-status. The node is not reachable and the system is trying to determine its status from firmware updates to its partner.

A detailed list of possible firmware statuses is provided after this table.

Node unreachable. The node is unreachable and its firmware status cannot be determined.
Takeover failed, reason: reason. Takeover of the partner node by the local node failed due to reason reason.
Previous giveback failed in module: module name. Auto giveback disabled due to exceeding retry counts. Previously attempted giveback failed in module module name. Automatic giveback is disabled.
  • Run the storage failover show-giveback command for more information.
Previous giveback failed in module: module name. Previously attempted giveback failed in module module name. Automatic giveback is not enabled by the user.
  • Run the storage failover show-giveback command for more information.
Connected to partner_name, Giveback of one or more SFO aggregates failed. The HA interconnect is active and can transmit data to the partner node. Giveback of one or more SFO aggregates failed and the node is in partial giveback state.
Waiting for partner_name, Partial giveback, Giveback of one or more SFO aggregates failed. The local node cannot exchange information with the partner node over the HA interconnect. Giveback of one or more SFO aggregates failed and the node is in partial giveback state.
Connected to partner_name, Giveback of SFO aggregates in progress. The HA interconnect is active and can transmit data to the partner node. Giveback of SFO aggregates is in progress.
  • Run the storage failover show-giveback command for more information.
Waiting for partner_name, Giveback of SFO aggregates in progress. The local node cannot exchange information with the partner node over the HA interconnect. Giveback of SFO aggregates is in progress.
  • Run the storage failover show-giveback command for more information.
Waiting for partner_name. Node owns aggregates belonging to another node in the cluster. The local node cannot exchange information with the partner node over the HA interconnect, and owns aggregates that belong to the partner node.
Connected to partner_name, Giveback of partner spare disks pending. The HA interconnect is active and can transmit data to the partner node. Giveback of SFO aggregates to the partner is done, but partner spare disks are still owned by the local node.
  • Run the storage failover show-giveback command for more information.
Connected to partner_name, Automatic takeover disabled. The HA interconnect is active and can transmit data to the partner node. Automatic takeover of the partner is disabled.
Waiting for partner_name, Giveback of partner spare disks pending. The local node cannot exchange information with the partner node over the HA interconnect. Giveback of SFO aggregates to the partner is done, but partner spare disks are still owned by the local node.
  • Run the storage failover show-giveback command for more information.
Waiting for partner_name. Waiting for partner lock synchronization. The local node cannot exchange information with the partner node over the HA interconnect, and is waiting for partner lock synchronization to occur.
Waiting for partner_name. Waiting for cluster applications to come online on the local node. The local node cannot exchange information with the partner node over the HA interconnect, and is waiting for cluster applications to come online.
Takeover scheduled. target node relocating its SFO aggregates in preparation of takeover. Takeover processing has started. The target node is relocating ownership of its SFO aggregates in preparation for takeover.
Takeover scheduled. target node has relocated its SFO aggregates in preparation of takeover. Takeover processing has started. The target node has relocated ownership of its SFO aggregates in preparation for takeover.
Takeover scheduled. Waiting to disable background disk firmware updates on local node. A firmware update is in progress on the node. Takeover processing has started. The system is waiting for background disk firmware update operations on the local node to complete.
Relocating SFO aggregates to taking over node in preparation of takeover. The local node is relocating ownership of its SFO aggregates to the taking-over node in preparation for takeover.
Relocated SFO aggregates to taking over node. Waiting for taking over node to takeover. Relocation of ownership of SFO aggregates from the local node to the taking-over node has completed. The system is waiting for takeover by the taking-over node.
Relocating SFO aggregates to partner_name. Waiting to disable background disk firmware updates on the local node. A firmware update is in progress on the node. Relocation of ownership of SFO aggregates from the local node to the taking-over node is in progress. The system is waiting for background disk firmware update operations on the local node to complete.
Relocating SFO aggregates to partner_name. Waiting to disable background disk firmware updates on partner_name. A firmware update is in progress on the node. Relocation of ownership of SFO aggregates from the local node to the taking-over node is in progress. The system is waiting for background disk firmware update operations on the partner node to complete.

Connected to partner_name. Previous takeover attempt was aborted because reason. Local node owns some of partner's SFO aggregates.

Reissue a takeover of the partner with the "-bypass-optimization" parameter set to true to takeover remaining aggregates, or issue a giveback of the partner to return the relocated aggregates.

The HA interconnect is active and can transmit data to the partner node. The previous takeover attempt was aborted because of the reason displayed under reason. The local node owns some of its partner's SFO aggregates.
  • Either reissue a takeover of the partner node, setting the -bypass-optimization parameter to true to takeover the remaining SFO aggregates, or perform a giveback of the partner to return relocated aggregates.

Connected to partner_name. Previous takeover attempt was aborted. Local node owns some of partner's SFO aggregates.

Reissue a takeover of the partner with the "-bypass-optimization" parameter set to true to takeover remaining aggregates, or issue a giveback of the partner to return the relocated aggregates.

The HA interconnect is active and can transmit data to the partner node. The previous takeover attempt was aborted. The local node owns some of its partner's SFO aggregates.
  • Either reissue a takeover of the partner node, setting the -bypass-optimization parameter to true to takeover the remaining SFO aggregates, or perform a giveback of the partner to return relocated aggregates.

Waiting for partner_name. Previous takeover attempt was aborted because reason. Local node owns some of partner's SFO aggregates.

Reissue a takeover of the partner with the "-bypass-optimization" parameter set to true to takeover remaining aggregates, or issue a giveback of the partner to return the relocated aggregates.

The local node cannot exchange information with the partner node over the HA interconnect. The previous takeover attempt was aborted because of the reason displayed under reason. The local node owns some of its partner's SFO aggregates.
  • Either reissue a takeover of the partner node, setting the -bypass-optimization parameter to true to takeover the remaining SFO aggregates, or perform a giveback of the partner to return relocated aggregates.

Waiting for partner_name. Previous takeover attempt was aborted. Local node owns some of partner's SFO aggregates.

Reissue a takeover of the partner with the "-bypass-optimization" parameter set to true to takeover remaining aggregates, or issue a giveback of the partner to return the relocated aggregates.

The local node cannot exchange information with the partner node over the HA interconnect. The previous takeover attempt was aborted. The local node owns some of its partner's SFO aggregates.
  • Either reissue a takeover of the partner node, setting the -bypass-optimization parameter to true to takeover the remaining SFO aggregates, or perform a giveback of the partner to return relocated aggregates.
Connected to partner_name. Previous takeover attempt was aborted because failed to disable background disk firmware update (BDFU) on local node. The HA interconnect is active and can transmit data to the partner node. The previous takeover attempt was aborted because the background disk firmware update on the local node was not disabled.
Connected to partner_name. Previous takeover attempt was aborted because reason. The HA interconnect is active and can transmit data to the partner node. The previous takeover attempt was aborted because of the reason displayed under reason.
Waiting for partner_name. Previous takeover attempt was aborted because reason. The local node cannot exchange information with the partner node over the HA interconnect. The previous takeover attempt was aborted because of the reason displayed under reason.
Connected to partner_name. Previous takeover attempt by partner_name was aborted because reason. The HA interconnect is active and can transmit data to the partner node. The previous takeover attempt by the partner node was aborted because of the reason displayed under reason.
Connected to partner_name. Previous takeover attempt by partner_name was aborted. The HA interconnect is active and can transmit data to the partner node. The previous takeover attempt by the partner node was aborted.
Waiting for partner_name. Previous takeover attempt by partner_name was aborted because reason. The local node cannot exchange information with the partner node over the HA interconnect. The previous takeover attempt by the partner node was aborted because of the reason displayed under reason.
Previous giveback failed in module: module name. Auto giveback will be initiated in number of seconds seconds. The previous giveback attempt failed in module module_name. Auto giveback will be initiated in number of seconds seconds.
  • Run the storage failover show-giveback command for more information.
Node owns partner's aggregates as part of the non-disruptive controller upgrade procedure. The node owns its partner's aggregates due to the non-disruptive controller upgrade procedure currently in progress.
Connected to partner_name. Node owns aggregates belonging to another node in the cluster. The HA interconnect is active and can transmit data to the partner node. The node owns aggregates belonging to another node in the cluster.
Connected to partner_name. Waiting for partner lock synchronization. The HA interconnect is active and can transmit data to the partner node. The system is waiting for partner lock synchronization to complete.
Connected to partner_name. Waiting for cluster applications to come online on the local node. The HA interconnect is active and can transmit data to the partner node. The system is waiting for cluster applications to come online on the local node.
Non-HA mode, reboot to use full NVRAM. Storage failover is not possible. The HA mode option is configured as non_ha.
  • You must reboot the node to use all of its NVRAM.
Non-HA mode, remove HA interconnect card from HA slot to use full NVRAM. Storage failover is not possible. The HA mode option is configured as non_ha.
  • You must move the HA interconnect card from the HA slot to use all of the node's NVRAM.
Non-HA mode, remove partner system to use full NVRAM. Storage failover is not possible. The HA mode option is configured as non_ha.
  • You must remove the partner controller from the chassis to use all of the node's NVRAM.
Non-HA mode. Reboot node to activate HA. Storage failover is not possible.
  • The node must be rebooted to enable HA capability.
Non-HA mode. See documentation for procedure to activate HA. Storage failover is not possible. The HA mode option is configured as non_ha.
  • You must run the storage failover modify -mode ha -node nodename command on both nodes in the HA pair and then reboot the nodes to enable HA capability.

Possible reasons automatic takeover is not possible

If automatic takeover is not possible, the reasons are displayed in the storage failover show command output. The output has the following form: Takeover of partner_name is not possible due to reason(s): reason1, reason2, ...

Possible values for reason are as follows:

Possible firmware states