Skip to main content
NetApp Knowledge Base

LIF found on base port of its home ifgrp after a non-graceful shutdown in ONTAP 9

Last Updated:

Applies to



  • 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.
    • In this event, you may find EMS errors such as:
[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. Use the "network port broadcast-domain show" command to identify a port in the same broadcast domain as port "CLUSTER-01:e0c"
[kern_vifmgr:info:5526] [0x8089b2800] [FailoverMgr::scanIncorrigibleVifs] LIF LIF_NAME (1000) has no available failover targets on this node.
  • Upon running network interface show -lif LIF_NAME -instance, you may see the following status:
Operational Status: down
Extended Status: This LIF is down because all failover targets are either down or otherwise unavailable. Use the "network interface show -failover" command to review the LIF's failover configuration.
  • You may also be unable to ping to or from the LIF in this case, indicated no network connectivity from that interface.


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.