Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 20 results
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_is_failing_when_one_node_LIFs_are_down
      Applies to ONTAP 9.x SnapMirror SnapMirror is failing with the error: Last Transfer Error: Failed to create Snapshot copysnapmirror.xxxxxxx.xxxxxxx on volume vserver:volume. (Failed to get volume attr...Applies to ONTAP 9.x SnapMirror SnapMirror is failing with the error: Last Transfer Error: Failed to create Snapshot copysnapmirror.xxxxxxx.xxxxxxx on volume vserver:volume. (Failed to get volume attributes for UUID:volume. (Volume location not found. Either the system is busy or the peer cluster is not Available. Wait a few minutes and try the operation again. If the volume is on a remote cluster, before retrying the operation, use the "cluster peer show" command to check the availability.))
    • https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/What_LIFs_are_used_for_intracluster_SnapMirror_volume_level_relationship
      Applies to ONTAP 9.x SnapMirror SnapVault Answer Intracluster SnapMirror uses the cluster interconnect to move data Intracluster throttle is supported, and it works the same way as the intercluster th...Applies to ONTAP 9.x SnapMirror SnapVault Answer Intracluster SnapMirror uses the cluster interconnect to move data Intracluster throttle is supported, and it works the same way as the intercluster throttle Prerequisites: SVM peering Interconnect between nodes Intercluster LIFs are not mandatory Additional Information SnapMirror configuration and best practices guide for ONTAP 9
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Unable_to_online_FCP_LIFs_after_headswap
      Applies to ONTAP 9 Issue Unable to online FCP LIFs after headswap. Error: command failed: Timeout: Operation "fcpLifUpdate_iterator::modify_imp()" took longer than 120 seconds to complete [from mgwd o...Applies to ONTAP 9 Issue Unable to online FCP LIFs after headswap. Error: command failed: Timeout: Operation "fcpLifUpdate_iterator::modify_imp()" took longer than 120 seconds to complete [from mgwd on node "NetApp-node" (VSID: -1) to bcomd at 127.0.0.1]
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Data_LIF_unavailable_after_changing_IP
      Applies to ONTAP 9 Issue After a data LIF IP is changed, the new IP cannot be reached
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Vscan_server_is_not_able_to_connect_to_the_ONTAP_because_the_Vserver_data_LIF_does_not_have_CIFS_configured_as_a_protocol
      Vscan server is not able to connect to the ONTAP because the Vserver data LIF does not have CIFS configured as a protocol
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/What_triggers_the_process_of_LIF_s_auto_revert
      Auto-reversion of cluster LIFs requires that the home port send a message that the port is up again before it attempts to process the reversion the LIF's -auto-revert parameter must be set to 'true' A...Auto-reversion of cluster LIFs requires that the home port send a message that the port is up again before it attempts to process the reversion the LIF's -auto-revert parameter must be set to 'true' An automatic process triggers the LIF's home port to send a message that the port is up again manual migrations of LIFs and manual up/down of ports will not trigger it The LIF's sticky bit is set to 'false' The sticky bit is a true/false flag that is set when a manual migration of the LIF is made
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Can_Ontap_CIFS_clients_survive_a_LIF_migrate
      SMB 2.0 and 2.1, the use of durable file handles allows the session to reconnect without any impact to the application: SMB 2 addresses this need with durable handles: file handles that are preserved ...SMB 2.0 and 2.1, the use of durable file handles allows the session to reconnect without any impact to the application: SMB 2 addresses this need with durable handles: file handles that are preserved by the client and can be used to reestablish disconnected sessions. Note: Although durable handles are nondisruptive for volume moves and LIF migrations, they are not mirrored across nodes, and a failover (or an upgrade) of a node results in the lock state being lost.
    • https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/Path_will_disconnect_and_reconnect_when_an_iSCSI_LIF_is_renamed
      Applies to ONTAP 9.3–9.7 iSCSI Issue The path will disconnect and reconnect when an iSCSI LIF is renamed
    • https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/Controller_Has_Only_One_Cluster_LIF_event_due_to_false_positives_by_AIQUM
      False event triggered in Active IQ Unified Manager (UM) 9.11 - “Controller Has Only One Cluster LIF"
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_configure_failover_group_and_targets_via_split_broadcast_domain_in_ONTAP_9
      Applies to ONTAP 9 Logical Interface (LIF) Broadcast domains in same IPSPACE Description This article describes the procedure that should be followed to configure Logical Interface (LIF) failover dest...Applies to ONTAP 9 Logical Interface (LIF) Broadcast domains in same IPSPACE Description This article describes the procedure that should be followed to configure Logical Interface (LIF) failover destinations in ONTAP 9
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/LIF_found_on_base_port_of_its_home_ifgrp_after_a_non-graceful_shutdown_in_ONTAP_9
      After a non-graceful shutdown (such as a power outage) and subsequent recovery, if a LIF was previously homed on single-port ifgrp, it may be found on the base port of its ifgrp. [vifmgr_virtual_inter...After a non-graceful shutdown (such as a power outage) and subsequent recovery, if a LIF was previously homed on single-port ifgrp, it may be found on the base port of its ifgrp. [vifmgr_virtual_interface_iterator::move_imp] Well-known error thrown while moving LIF LIF_NAME (1000): Failed to update LIF "LIF_NAME" because port "CLUSTER-01:a0a" is in a different broadcast domain than the LIF's home port.