Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 8 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Error_The_specified_port_is_not_assigned_to_Default_IPspace_when_adding_a_port_to_an_Interface_Group
      Applies to ONTAP 9.5 IPspace Interface Group (ifgrp) Issue Adding a port to an Interface Group, error appears: ::*> network port ifgrp add-port -node <node_name> -ifgrp a0a -port e0g Error: command fa...Applies to ONTAP 9.5 IPspace Interface Group (ifgrp) Issue Adding a port to an Interface Group, error appears: ::*> network port ifgrp add-port -node <node_name> -ifgrp a0a -port e0g Error: command failed: Specified port is not assigned to Default IPspace.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Network_interface_migrate_fails_when_moving_SVM_to_new_vLAN_in_ONTAP_9
      Applies to ONTAP 9.X Issue Error received when attempting to run network interface modify fails: Error: command failed: Port must reside in the same IPspace as the vserver of the Lif.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/ONTAP_reporting_link_down_on_internal_loopback_interface
      Applies to NetApp Active IQ Unified Manager ONTAP 9 Issue ONTAP reporting link down on internal loopback interface This will also create an event in Active IQ Unified Manager EMS message example: Sun ...Applies to NetApp Active IQ Unified Manager ONTAP 9 Issue ONTAP reporting link down on internal loopback interface This will also create an event in Active IQ Unified Manager EMS message example: Sun Feb 27 20:22:04 +0000 [cluster1-01: mgwd: netif.linkDown:info]: Ethernet lo0: Link down, check cable.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Vserver_Lif_unreachable_after_Failover_due_to_incorrect_IPspace_configuration
      Applies to ONTAP 9 IPspace Failover Issue When a node goes down and/or a Lif fails over to another node, the Vserver/Lif is not reachable anymore Vserver is not configured in any IPspace, so will be i...Applies to ONTAP 9 IPspace Failover Issue When a node goes down and/or a Lif fails over to another node, the Vserver/Lif is not reachable anymore Vserver is not configured in any IPspace, so will be in Default IPspace Default IPspace does not have any (functionally identical) network ports, to which the Lif can failover to
    • https://kb.netapp.com/on-prem/ontap/DP/NDMP/NDMP-KBs/NDMP_Cluster_Aware_Backup_cannot_use_Intercluster_LIF_s_when_LIF_or_SVM_reside_within_non_default_IPSpace
      Applies to ONTAP 9 NDMP Cluster Aware Backup (CAB) Issue SVM configured in non-default IPSpace using SVM scoped NDMP backups may fail. InterCluster LIF configured in non-default IPSpace using SVM scop...Applies to ONTAP 9 NDMP Cluster Aware Backup (CAB) Issue SVM configured in non-default IPSpace using SVM scoped NDMP backups may fail. InterCluster LIF configured in non-default IPSpace using SVM scoped NDMP backups may fail. The ndmp logs will show the following error : [kern_ndmpd:info:3442] [30588] DEBUG: LOG sev (3) msg (NDMP Vserver Connect: couldn't find any appropriate preferred local src IP address)
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_modify_SVM_IPspace_for_ONTAP_9
      Applies to ONTAP 9 Description An IPspace on an SVM (vserver) needs to be changed. You cannot modify the IPspace after creation, but you can create a new SVM and assign it a new IPspace.
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_update_failed_after_ONTAP_upgrade_with_error__CSM__Connection_aborted
      Applies to ONTAP 9 SnapMirror IPspace Issue After ONTAP upgrade SnapMirror update fails with error: Transfer for volume "<vol_name>" failed. Reason: Failed to create Snapshot copy <snapshot_name> on v...Applies to ONTAP 9 SnapMirror IPspace Issue After ONTAP upgrade SnapMirror update fails with error: Transfer for volume "<vol_name>" failed. Reason: Failed to create Snapshot copy <snapshot_name> on volume <svm_name:volume_name>. (CSM:Connection aborted.)
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/Fail_to_sync_onboard_key_management_keys_on__partner_cluster_of_MetroCluster_IP
      After setting up Onboard Key Manager in siteA of MetroCluster IP, fails to sync the keys on siteB of MetroCluster IP via the command security key-manager onboard sync with the following error messages...After setting up Onboard Key Manager in siteA of MetroCluster IP, fails to sync the keys on siteB of MetroCluster IP via the command security key-manager onboard sync with the following error messages: Use the "security key-manager onboard enable" command to enable the Onboard Key Manager and then try again. Run the "security key-manager onboard sync" with the same passphrase before proceeding with any key manager operations.