Skip to main content
NetApp Knowledge Base

X1151A ports hang during ONTAP upgrade

Views:
904
Visibility:
Public
Votes:
1
Category:
aff-series
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • AFF A400
  • X1151A - 2p 100GbE Smart IO QSFP28 Cu|Op
  • IONIC card firmware 1.0.1-E-31 through 1.4.0-E-96

Issue

  • In rare conditions, ports on the X1151A IONIC network interface card (NIC) might stop responding, even if the status of network ports is up:
slot 3: 100G Ethernet Controller IONIC
e3a MAC Address: xx:xx:xx:xx:xx:xx (auto-100g_cr4-fd-up)
QSFP Vendor: Molex
QSFP Part Number: 112-00573
QSFP Serial Number: QSFP_serial_number
e3b MAC Address: xx:xx:xx:xx:xx:xx (auto-100g_cr4-fd-up)
QSFP Vendor: Molex
QSFP Part Number: 112-00573
QSFP Serial Number: QSFP_serial_number
Device Type: ionic
Firmware Version: 1.0.1-E-31
Serial Number: serial_number
  • Node may not show any cluster interface info with net int show.
  • Network port show -role cluster show a "-" for the two interfaces that should be up.

Examples :

NodeA::> net int show
(network interface show)
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
clus        Node2_mgmt up/up      10.6.34.54/24      Node1         e0M     true
  <<< missing cluster interfaces

clus::> network port show -role cluster

Warning: Unable to list entries for vifmgr on node "Node1": RPC: Couldn't make connection [from mgwd on node "Node2" (VSID: -1) to vifmgr at 169.254.212.1].
Node: Node1
Speed(Mbps) Health
Port      IPspace      Broadcast Domain Link MTU Admin/Oper   Status
--------- ------------ ---------------- ---- ---- ----------- --------
e3a       Cluster      -                -    9000 auto/-      -
e3b       Cluster      -                -    9000 auto/-      -
2 entries were displayed.

  • Node that was taken over during the upgrade may show both e3a/e3b ports as down.
  • Attempting to reboot the upgraded node again results in the same failure.

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.