Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Linux_NFS_client_lost_connection_after_SVM_migration_by_SnapMirror_volume_replication
      Applies to ONTAP 9 SnapMirror Storage Virtual Machine Disaster Recovery (SVM DR) Issue Linux NFS clients lost connection to export volumes after SVM migration by SnapMirror volume replication A reboot...Applies to ONTAP 9 SnapMirror Storage Virtual Machine Disaster Recovery (SVM DR) Issue Linux NFS clients lost connection to export volumes after SVM migration by SnapMirror volume replication A reboot of the NFS client could restore the connection
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Fails_to_abort_vserver_migrate_operation_with_error_stauts_migrate_abort_failed
      For some reason, the unfinished vserver migration was aborted by the following command: The vserver migrate show reports the following error status and details: Reason: Failed to delete SnapMirror rel...For some reason, the unfinished vserver migration was aborted by the following command: The vserver migrate show reports the following error status and details: Reason: Failed to delete SnapMirror relationship for Vserver The snapmirror list-destination command does not show the SnapMirror relationship that exists The commands snapmirror release or snapmirror delete both report "Error:command failed: Invalid xxxx SnapMirror Consistency Group name ""."
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SVM_migration_finds_no_network_ports_to_confirm_reachability
      Reason: There are no network ports on the destination cluster "Cluster01" where reachability is confirmed for the following IP addresses: 10.0.000.00, 200.00.0.00, 30.0.00.00. To change the source Vse...Reason: There are no network ports on the destination cluster "Cluster01" where reachability is confirmed for the following IP addresses: 10.0.000.00, 200.00.0.00, 30.0.00.00. To change the source Vserver configuration, use the "vserver migrate pause" command on the destination cluster, make the configuration changes on the source cluster, and then use the "vserver migrate resume" command on the destination cluster.