Skip to main content
NetApp Knowledge Base

IFGRP down with flapping member ports

  1. Last updated
  2. Save as PDF
Views:
1,291
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS8200
  • ONTAP 9.3P5
  • 2 node Metrocluster

Issue

  • IFGRP used in LACP configuration goes down
  • IFGRP member ports e0a/e0b are connected to different switches
  • Ports intermittently transition from up to down state, then recover
  • Messages observed on the system:

7/7/2021 22:46:51 node-01 ALERT vifmgr.lifdown.noports: LIF node_icl1 (on virtual server 4294967295), IP address XXX.XXX.XXX.XXX, currently cannot be hosted on node node-01, port a0a-2, or any of its failover targets, and is being marked as down.

7/7/2021 22:46:38 node-01 ALERT vifmgr.lifdown.noports: LIF intercluster_n1 (on virtual server 4294967295), IP address XXX.XXX.XXX.XXX, currently cannot be hosted on node node-01, port a0a-2, or any of its failover targets, and is being marked as down.

7/7/2021 22:46:35 node-01 ERROR net.ifgrp.lacp.link.inactive: ifgrp a0a, port e0b has transitioned to an inactive state. The interface group is in a degraded state.

7/7/2021 22:46:35 node-01 ERROR net.ifgrp.lacp.link.inactive: ifgrp a0a, port e0a has transitioned to an inactive state. The interface group is in a degraded state.

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.