Skip to main content
NetApp Knowledge Base

LIF placement error due to network port issue

Views:
30
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster 

  • ONTAP 9 

Issue

  • LIF Placement Errors present in metrocluster check lif show:

 IFS_Gent-mc 
                                lif_CIFS_Gent_1 
                                             lif-placed-on-dr-node  ok 
                                             port-selection         warning 

  • EMS reporting network port issues:

Tue Jul 18 06:06:50 +0000 [ClusterM-01: vifmgr: vifmgr.lifmoved.linkdown:notice]: LIF lif_CIFS_Gent_1 (on virtual server 9), IP address 192.168.21.240, is being moved to node Cluster-02, port e0g-58. 
Tue Jul 18 06:06:50 +0000 [ClusterM-01: vifmgr: vifmgr.reach.noreach:notice]: Network port e0g-58 on node ClusterM-01 cannot reach its expected broadcast domain Default:BD_58. No other broadcast domains appear to be reachable from this port. 
Tue Jul 18 06:06:50 +0000 [ClusterM-01: vifmgr: vifmgr.reach.skipped:notice]: Network port e0g-58 on node ClusterM-01 was not scanned for reachability because it was administratively or operationally down at the time of the scan. 
Tue Jul 18 06:06:53 +0000 [ClusterM-01: vifmgr: vifmgr.portdown:notice]: A link

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.