Skip to main content
NetApp Knowledge Base

Port showing state lag_inactive post switch migration activity

Views:
994
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
HW
Last Updated:

Applies to

  • FAS3220
  • Quad Gigabit Ethernet Controller 8258
  • Cisco Catalyst 4510
  • Ontap 8.2.5P3 7-mode

Issue

  • A port is showing as state lag_inactive in an IFGRP after moving it to a new switch.

lag_inactive:
e6b: state lag_inactive, since 05Jul2024 12:33:42 (35+10:17:05)
                mediatype: auto-1000t-fd-up
                flags: lacp enabled
                input packets 0, input bytes 0
                input lacp packets 32xxx3, output lacp packets 36xxxx69
                output packets 63xx2, output bytes 7xxxx73
                up indications 36, broken indications 33
                drops (if) 0, drops (link) 0, drops (no active link) 0
                indication: lag_inactive at 05Jul2024 12:33:42
                        consecutive 0, transitions 69

  • The port is physically up and is not faulty.
  • The issue remains on the same filer interface port when moving to a different switch port.
  • The interface port "hungs-up" when the cable is re-plugged to a new switch.
  • As a troubleshooting steps below can be performed before proceeding with solution.
    • Check the status of the interfaces before and after the switch change.
    • Reseat the cable connections to the new switch.
    • Try to use another switch port on the new switch.
    • Change back to the old switch to see if the error appears again for the same filer port.

 

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.