Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 20 results
    • ONTAP Select instance goes unexpectedly into takeover
      https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/ONTAP_Select_instance_goes_unexpectedly_into_takeover
      Applies to NetApp ONTAP Select ESXi Issue An ONTAP Select instance in an HA pair has unexpectedly gone into Takeover- An additional CLTFLT:HA Group Notification from SelectNode1-1 (CONTROLLER TAKEOVER...Applies to NetApp ONTAP Select ESXi Issue An ONTAP Select instance in an HA pair has unexpectedly gone into Takeover- An additional CLTFLT:HA Group Notification from SelectNode1-1 (CONTROLLER TAKEOVER COMPLETE AUTOMATIC) ALERT has been reported for this system. In some cases, adapter error prevents command from being sent to device error messages might appear within EMS log
    • kernel hang panic occurred from OpenStack instance during storage takeover
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/kernel_hang_panic_occurred_from_OpenStack_virtual_machine__during_storage_takeover
      Applies to ONTAP 9 OpenStack Issue kernel hang panic occurred from OpenStack instance(virtual machine) during storage takeover
    • Takeover impossible and NVRAM log not synchronized in CVO as interconnect was down
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/Takeover_impossible_and_NVRAM_log_not_synchronized_in_CVO_as_interconnect_was_down
      Cloud Volumes ONTAP (CVO) HA Interconnect is down e0c port is with no carrier status Cluster01::> node run -node * -command ifconfig inet X.X.X.X netmask 0xffffff00 broadcast 10.196.6.255 Services: 0x...Cloud Volumes ONTAP (CVO) HA Interconnect is down e0c port is with no carrier status Cluster01::> node run -node * -command ifconfig inet X.X.X.X netmask 0xffffff00 broadcast 10.196.6.255 Services: 0x00000180 Vserver ID: -5 cluster01::> storage failover show -fields interconnect-links ,interconnect-up, interconnect-type node interconnect-up interconnect-links interconnect-type cluster01-01 false RDMA Interconnect is down iWARP cluster01-02 false RDMA Interconnect is down iWARP
    • AFF or FAS system does not detect partner causing failover
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/AFF_or_FAS_system_does_not_detect_partner_causing_failover
      [Nodeb: kernel: netif.linkDown:info]: Ethernet e0a: Link down, check cable. [Nodeb: wafl_exempt17: nvmm.mirror.aborting:debug]: mirror of sysid 1, partner_type HA Partner and mirror state NVMM_MIRROR_...[Nodeb: kernel: netif.linkDown:info]: Ethernet e0a: Link down, check cable. [Nodeb: wafl_exempt17: nvmm.mirror.aborting:debug]: mirror of sysid 1, partner_type HA Partner and mirror state NVMM_MIRROR_ONLINE is aborted because of reason NVMM_ERR_IO. ...[Nodeb: cf_main: cf.fsm.takeover.noHeartbeat:alert]: Failover monitor: Takeover initiated after no heartbeat was detected from the partner node. [Nodeb: cf_takeover: cf.fm.takeoverStarted:notice]: Failover monitor: takeover started
    • Does aborted SnapMirror try to transfer again by takeover or giveback?
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Does_aborted_SnapMirror_try_to_transfer_again_by_takeover_or_giveback
      ONTAP always retries aborted SnapMirrors after takeover/giveback as SnapMirror transfer can be aborted by takeover/giveback action SnapMirror relationships that are in an uninitialized state will not ...ONTAP always retries aborted SnapMirrors after takeover/giveback as SnapMirror transfer can be aborted by takeover/giveback action SnapMirror relationships that are in an uninitialized state will not retry after the reboot SnapMirror relationships in an uninitialized state will start to transfer, picking up from the checkpoint, only when a snapmirror initialize command is run for them snapmirror resume will need to be run to allow updates again
    • Can you create a new volume when a CVO HA cluster is in takeover?
      https://kb.netapp.com/Cloud/BlueXP/Cloud_Manager/Can_you_create_a_new_volume_when_a_CVO_HA_cluster_is_in_takeover
      Applies to Cloud Volumes ONTAP (CVO) Cloud Manager Answer Many cluster admin functions are disabled in Cloud Manager including aggregate creation or volume creation when the system is in takeover. Onc...Applies to Cloud Volumes ONTAP (CVO) Cloud Manager Answer Many cluster admin functions are disabled in Cloud Manager including aggregate creation or volume creation when the system is in takeover. Once the cluster is back in full HA status, Cloud Manager re-enables the ability for actions such as volume creation or similar cluster admin tasks. Additional Information
    • CIFS and NFS access fails while in failover due to difference in Preferred DCs (7-Mode)
      https://kb.netapp.com/Legacy/ONTAP/7Mode/CIFS_and_NFS_access_fails_while_in_failover_due_to_difference_in_Preferred_DCs_7_Mode
      Applies to Data ONTAP 7-Mode CIFS Issue After a failover, CIFS/NFS authentication cannot occur and data is inaccessible CIFS mounts timeout when attempting to mount NFS mounts can browse root volume b...Applies to Data ONTAP 7-Mode CIFS Issue After a failover, CIFS/NFS authentication cannot occur and data is inaccessible CIFS mounts timeout when attempting to mount NFS mounts can browse root volume but not any data volumes and appear to hang
    • IO interrupted during takeover
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/IO_interrupted_during_takeover
      Tue Nov 19 19:12:24 [node-01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF data_lif1_node1 (on virtual server 3), IP address xx.xxx.xx.81, is now hosted on node node-01, port a2a. Tue Nov 19 19:12...Tue Nov 19 19:12:24 [node-01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF data_lif1_node1 (on virtual server 3), IP address xx.xxx.xx.81, is now hosted on node node-01, port a2a. Tue Nov 19 19:12:24 [node-01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF data_lif1_node2 (on virtual server 3), IP address xx.xxx.xx.82, is now hosted on node node-01, port a2a.
    • Data LIF of the takeover node briefly disconnects during node takeover
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Data_LIF_of_the_takeover_node_briefly_disconnects_during_node_takeover
      Sun Feb 13 16:12:17 +0100 [node01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF node02-cifs (on virtual server 3), IP address 10.20.20.10, is now hosted on node node01, port a0d. Sun Feb 13 16:12:...Sun Feb 13 16:12:17 +0100 [node01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF node02-cifs (on virtual server 3), IP address 10.20.20.10, is now hosted on node node01, port a0d. Sun Feb 13 16:12:17 +0100 [node01: vifmgr: vifmgr.lifsuccessfullymoved:notice]: LIF node02-nfs (on virtual server 3), IP address 10.20.21.8, is now hosted on node node01, port a0d.
    • (CONTROLLER TAKEOVER COMPLETE AUTOMATIC) ALERT due to halted node
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/CONTROLLER_TAKEOVER_COMPLETE_AUTOMATIC_ALERT_due_to_halted_node
      CONTROLLER TAKEOVER COMPLETE AUTOMATIC alert due to halted node
    • ONTAP Select reports Error: Mailbox disks are not healthy
      https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/ONTAP_Select_reports_Error__Mailbox_disks_are_not_healthy
      [Toaster_01: statd: cf.takeover.disabled:alert]: HA mode, but takeover of partner is disabled due to reason : Mailbox disks are not healthy. [Toaster_01: kernel: iscsi.session.stateChanged:notice]: iS...[Toaster_01: statd: cf.takeover.disabled:alert]: HA mode, but takeover of partner is disabled due to reason : Mailbox disks are not healthy. [Toaster_01: kernel: iscsi.session.stateChanged:notice]: iSCSI session state is changed to Reconnecting (destroy sim) for the target iqn.2012-05.local:mailbox.target.select00001 (type: mailbox, address: 10.xx.xx.xx).