Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 8 results
    • Azure CVO HA -"cf.fsm.takeoverOfPartnerDisabled" takeover of NODE disabled (unsynchronized log)
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/Azure_CVO_HA_cf_fsm_takeoverOfPartnerDisabled_takeover_of_NODE_disabled_unsynchronized_log
      Applies to Microsoft Azure Cloud Volumes ONTAP(CVO) High Availablity(HA) ONTAP 9.9.1, 9.10.0 Unsynchronized logs Unplanned takeover failure Issue On Azure CVO HA, after ONTAP upgrade to 9.9.1 or 9.10....Applies to Microsoft Azure Cloud Volumes ONTAP(CVO) High Availablity(HA) ONTAP 9.9.1, 9.10.0 Unsynchronized logs Unplanned takeover failure Issue On Azure CVO HA, after ONTAP upgrade to 9.9.1 or 9.10.0 customer sees error message takeover of <NODE> disabled (unsynchronized log). EMS.log: Sun Jan 00 00:00:00 +0000 [AzureCVOHA-01: cf_main: cf.fsm.takeoverOfPartnerDisabled:error]: Failover monitor: takeover of AzureCVOHA-01-02 disabled (unsynchronized log).
    • EMERGENCY Controller failover of node_name is not possible. Unsynchronized log
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/EMERGENCY_Controller_failover_of_node_name_is_not_possible._Unsynchronized_log
      4/8/2021 08:29:15 node_name_1 ERROR cf.fsm.takeoverByPartnerDisabled: Failover monitor: takeover of node_name_1 by node_name_2 disabled (HA interconnect error. 4/8/2021 07:49:11 node_name_1 ERROR cf.f...4/8/2021 08:29:15 node_name_1 ERROR cf.fsm.takeoverByPartnerDisabled: Failover monitor: takeover of node_name_1 by node_name_2 disabled (HA interconnect error. 4/8/2021 07:49:11 node_name_1 ERROR cf.fsm.takeoverByPartnerDisabled: Failover monitor: takeover of node_name_1 by node_name_2 disabled (HA interconnect error. Verify that the partner node is running and that the HA interconnect cabling is correct, if applicable.
    • Failover not possible: unsynchronized log and "disk inventory not exchanged" after adding AFF A320 nodes to cluster
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Failover_not_possible__unsynchronized_log_and_disk_inventory_not_exchanged_after_adding_AFF_A320_nodes_to_cluster
      Switched cluster with existing non AFF A320 nodes AFF A320 nodes report takeover is disabled due to unsynchronized log in EMS: monitor.globalStatus.critical: Controller failover of <node> is not possi...Switched cluster with existing non AFF A320 nodes AFF A320 nodes report takeover is disabled due to unsynchronized log in EMS: monitor.globalStatus.critical: Controller failover of <node> is not possible: unsynchronized log. cf.fsm.takeoverOfPartnerDisabled: Failover monitor: takeover of <node> disabled (unsynchronized log). Waiting for <partner-node>, Takeover is not possible: Storage failover interconnect error, NVRAM log not synchronized, Disk inventory not exchanged
    • DR Mirrors not operational on FAS8200/AFF A300 after brief connectivity loss
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/DR_Mirrors_not_operational_on_FAS8200_AFF_A300_after_brief_connectivity_loss
      name=wafl qp_id=0 state=DISCONNECTED rhp=0xfffff806190ed800 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client p_name=wafl state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12 name=wafl qp_id=0 state=CONNECT...name=wafl qp_id=0 state=DISCONNECTED rhp=0xfffff806190ed800 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client p_name=wafl state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12 name=wafl qp_id=0 state=CONNECTING rhp=0xfffff8086ce41800 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client p_name=wafl state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=-12 name=raid qp_id=0 state=CONNECTING rhp=0xfffff8029f887000 refcnt=0 last_err=12 sq=0 rq=0 tid=0 cq=0 client p_name=raid state=WAIT_FOR_CONN rhp=0 refcnt=0 last_err=…
    • Takeover status is flapping between Disabled and Enabled due to unstable HA interconnect link
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Takeover_status_is_flapping_between_Disabled_and_Enabled_due_to_unstable_HA_interconnect_link
      The failover is disabled and enabled automatically between a HA pair due to unstable HA interconnect link: [Netapp1-01: cf_main: cf.fsm.takeoverByPartnerDisabled:error]: Failover monitor: takeover of ...The failover is disabled and enabled automatically between a HA pair due to unstable HA interconnect link: [Netapp1-01: cf_main: cf.fsm.takeoverByPartnerDisabled:error]: Failover monitor: takeover of Netapp1-01 by Netapp1-02 disabled (unsynchronized log) [Netapp1-01: cf_main: cf.fsm.takeoverByPartnerEnabled:notice]: Failover monitor: takeover of Netapp1-01 by Netapp1-02 enabled
    • ONTAP Select node boot error Waiting for requisite number of Mailboxes
      https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/ONTAP_Select_node_boot_error_Waiting_for_requisite_number_of_Mailboxes
      When you open the vCenter console for each Select Node VM, one or both show a boot loader message Waiting for requisite number of Mailboxes. Deploy UI may display the following error:page cannot be fo...When you open the vCenter console for each Select Node VM, one or both show a boot loader message Waiting for requisite number of Mailboxes. Deploy UI may display the following error:page cannot be found" or "502 Bad Gateway. Logging in to the Deploy UI (either through console or SSH) the following error may be displayed: NetApp ONTAP Select Deploy Utility. Deploy API service is currently not available. (Press Ctrl-C to continue to the shell) <center><h1>502 Bad Gateway</h1></center>
    • Azure Cloud Volumes ONTAP takeover impossible due to unsynchronized logs
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/Azure_Cloud_Volumes_ONTAP_takeover_impossible_due_to_unsynchronized_logs
      There are EMS errors stating failover is not possible due to interconnect errors Sat Aug 15 03:07:50 -0700 [clusterAnode1: monitor: monitor.globalStatus.critical:EMERGENCY]: Controller failover of gvm...There are EMS errors stating failover is not possible due to interconnect errors Sat Aug 15 03:07:50 -0700 [clusterAnode1: monitor: monitor.globalStatus.critical:EMERGENCY]: Controller failover of gvmx2pontapcloudha2-01 is not possible: HA interconnect error. Verify that the partner node is running and that the HA interconnect cabling is correct, if applicable. Errors such as the following are logged prior to the interconnect errors
    • CVO Azure: Controller Failover of node is not possible: unsynchronized log
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/CVO_Azure__Controller_Failover_of_node_is_not_possible__unsynchronized_log
      Applies to Cloud Volumes ONTAP (CVO) Microsoft Azure Unsynchronized log Issue Customer receives an alert for the following: "Source: my_node1 Severity: critical Message: Controller failover of my_node...Applies to Cloud Volumes ONTAP (CVO) Microsoft Azure Unsynchronized log Issue Customer receives an alert for the following: "Source: my_node1 Severity: critical Message: Controller failover of my_node1 is not possible: unsynchronized log. "