Skip to main content
NetApp Knowledge Base

What can cause a Takeover due to network partition

Views:
85
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • NetApp Cloud Volumes ONTAP
  • NetApp ONTAP Select
  • Virtual Storage Appliance
  • Software-Defined Storage
  • High Availability

Answer

Takeover due to network partition occurs when cluster network and one of either HA interconnect or RAID sync mirror goes down

 

Event Severity Description
EMS_ha_netPartition_reboot NOTICE

This message occurs when a Data ONTAP(R) subsystem detects an error potentially due to network partitioning, including no connectivity to the mediator, and reboots the local node due to the network partition. The reboot occurs only if takeover-by-partner is enabled on the local node.

A reboot will occur only if a node connection to the mediator was down when an NVRAM or RSM error was detected.

EMS_ha_netPartition_takeover NOTICE This message occurs when a Data ONTAP(R) subsystem detects an error potentially due to network partitioning and initiates a takeover of the partner node due to the partition.
EMS_ha_netPartition NOTICE This message occurs when a Data ONTAP(R) subsystem detects an error potentially due to network partitioning but is not able to takeover the partner node nor allow the partner to takeover because both takeover-of-partner and takeover-by-partner are both disabled.
EMS_ha_netPartition_other DEBUG This message occurs when concurrent errors are detected on more than one of a node's interfaces, but the errors are due to an in-progress halt, reboot, takeover or similar action affecting network connectivity.
EMS_cf_fsm_takeover_netPartition DEBUG This message occurs when a takeover is initiated due to potential network partitioning.

 

Scan to view the article on your device