Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 12 results
    • SnapMirror updates fail after IP change with CSM: Connection aborted
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_updates_fail_after_IP_change_with_CSM__Connection_aborted
      SnapMirror fails with Error: Failed to get transfer Snapshot information from source volume "SVM:vol1". (CSM: Connection aborted.) Cluster peer ping reports the old IP is unreachable Cluster1::> clust...SnapMirror fails with Error: Failed to get transfer Snapshot information from source volume "SVM:vol1". (CSM: Connection aborted.) Cluster peer ping reports the old IP is unreachable Cluster1::> cluster peer ping Node: Cluster1-n1 Destination Cluster: Cluster2 Node: Cluster1-n1 Destination Cluster: Cluster1 Error: No intercluster LIFs are available on node "Cluster1-n1". Node: Cluster1-n1 Destination Cluster: sfsecn000202 Destination Node IP Address Count TTL RTT(ms) Status
    • SnapMirror show command show a source vserver name that does not exist on source
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_show_command_show_a_source_vserver_name_that_does_not_exist_on_source
      Applies to ONTAP 9 Vserver peering SnapMirror Issue On destination the output of snapmirror show return a name for source vserver that doesn't exist on the source. Example On destination: cluster2::> ...Applies to ONTAP 9 Vserver peering SnapMirror Issue On destination the output of snapmirror show return a name for source vserver that doesn't exist on the source. Example On destination: cluster2::> snapmirror show Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated source:vol1 XDP svm2:vol_vol1_dest Snapmirrored Idle - true - On source: cluster1::> vserver show -vserver source there are no entries matching your query.
    • Cluster peer create or modify fails with error: Remote system error no route to host
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Cluster_peer_create_or_modify_fails_with_error__Remote_system_error_no_route_to_host
      Applies to ONTAP 9 SnapMirror Issue Cluster peer create command fails with error: Error: command failed: Using peer-address xx.xx.xx.xx: An introductory RPC to the peer address "xx.xx.xx.xx" failed to...Applies to ONTAP 9 SnapMirror Issue Cluster peer create command fails with error: Error: command failed: Using peer-address xx.xx.xx.xx: An introductory RPC to the peer address "xx.xx.xx.xx" failed to connect: RPC: Remote system error - No route to host. Verify that the peer address is correct and try again. “
    • Cluster peer create fails with Error: RPC remote system error or time out
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Cluster_peer_create_fails_with_Error__RPC_remote_system_error_or_time_out
      Applies to 8.3 .X Cluster-Mode 9.X Cluster-Mode Issue Attempting to create a peering relationship between two peers results in an RPC error despite being able to ping successfully
    • Unable to Peer with remote cluster despite full connectivity
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/Unable_to_Peer_with_remote_cluster_despite_full_connectivity
      Applies to ONTAP 9 Issue Clusters peering from physical or cloud environments will show peer unavailable despite all intercluster LIFs being in full mesh.
    • METROCLUSTER SWITCHOVER FAILED - Internal error. Unable to migrate Vserver peer relationships
      https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/METROCLUSTER_SWITCHOVER_FAILED_-_Internal_error._Unable_to_migrate_Vserver_peer_relationships
      SnapMirror peer down during switchover / switchback Autosupports METROCLUSTER SWITCHOVER FAILED after switchover/switchback is initiated: Unable to migrate Vserver peer relationships. Reason: (Failed ...SnapMirror peer down during switchover / switchback Autosupports METROCLUSTER SWITCHOVER FAILED after switchover/switchback is initiated: Unable to migrate Vserver peer relationships. Reason: (Failed to communicate with peer cluster "<external_cluster>".). This issue only affects SnapMirror/SnapVault following the otherwise successful switchover
    • GCP: CVO launch filure "connection attempt to x:x:xx:xxx:443 failed"
      https://kb.netapp.com/Cloud/Cloud_Volumes_ONTAP/GCP__CVO_launch_filure_connection_attempt_to_x_x_xx_xxx_443_failed
      Applies to NetApp Cloud Manager (Connector) NetApp Cloud Volumes ONTAP (CVO) Google Cloud Platform (GCP) Issue Launching a new CVO in GCP fails with the following error: Errors in Timeline: "_failure"...Applies to NetApp Cloud Manager (Connector) NetApp Cloud Volumes ONTAP (CVO) Google Cloud Platform (GCP) Issue Launching a new CVO in GCP fails with the following error: Errors in Timeline: "_failure": "ErrorClosed(Connection reset by peer)", "newPassword": "*****", "svmName": "Default", "_cluster": "xx.x.xx.xxx", "_failure": "Connection attempt to xx.x.xx.xxx:443 failed", "userName": "admin"
    • Loop detected in next() for table jm_sched_keys in destination after peer deletion
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Loop_detected_in_next_for_table_jm_sched_keys_in_destination_after_peer_deletion
      Error: show failed on cluster "cluster1" vserver "cluster1" name "weekly_snap1": Loop detected in Rather than displaying the cluster name in columns or fields where the cluster name normally appears, ...Error: show failed on cluster "cluster1" vserver "cluster1" name "weekly_snap1": Loop detected in Rather than displaying the cluster name in columns or fields where the cluster name normally appears, the cluster serial number is displayed, instead. Both the local cluster name as well as the recently deleted peer cluster name appear in columns or fields that normally contain the cluster name, and the peer cluster name is associated with duplicate schedule names.
    • Switchback failing - the online status of the replication units in the cluster could not be verified
      https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/Switchback_failing_-_the_online_status_of_the_replication_units_in_the_cluster_could_not_be_verified
      Errors: Failed to set up the node and cluster components for the switchback operation. ClusterA (fatal): The MetroCluster DR operation was terminated because the online status of the replication units...Errors: Failed to set up the node and cluster components for the switchback operation. ClusterA (fatal): The MetroCluster DR operation was terminated because the online status of the replication units in the cluster could not be verified. Run the (privilege: advanced) "cluster ring show" command to display the status of the replication units. Try the MetroCluster DR operation again when each replication unit's "online" field shows either "master" or "secondary".
    • Cannot peer Workflow Automation with Unified Manager, error "cannot determine the unique ID of Unified Manager version from Workflow Automation host"
      https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/Cannot_peer_WFA_with_Unified_Manager_error_cannot_determine_the_unique_ID_of_Unified_Manager_version_from_Workflow_Automation_host
      Active IQ Unified Manager 9.6+ (AIQ UM) Trying to save the settings to enable peering between Unified Manager with WFA fails with error message: Due to an internal error, cannot determine the unique I...Active IQ Unified Manager 9.6+ (AIQ UM) Trying to save the settings to enable peering between Unified Manager with WFA fails with error message: Due to an internal error, cannot determine the unique ID of Unified Manager version <version> from Workflow Automation host <hostname> Due to an internal error, cannot determine the unique ID of ActiveIQ Unified Manager version <version> from Workflow Automation host <hostname> If Unified Manager is already peered Unified Manager stops updating.
    • Cluster peer unavailable alerts cpeer.addr.warn.host:alert
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Cluster_peer_unavailable_alerts_cpeer.addr.warn.host_alert
      Mon Jun 22 02:21:00 +08 [[cluster name]: mgwd: cpeer.addr.warn.host:alert]: Address [IP address] is not any of the addresses that peer cluster [cluster name] considers valid for the cluster peer relat...Mon Jun 22 02:21:00 +08 [[cluster name]: mgwd: cpeer.addr.warn.host:alert]: Address [IP address] is not any of the addresses that peer cluster [cluster name] considers valid for the cluster peer relationship; Details: An introductory RPC to the peer address "[IP address]" failed to connect: RPC: Remote system error [from mgwd on node "[cluster name] " (VSID: -3) to xcintro at [IP address]].