Skip to main content
NetApp Knowledge Base

Controller Unresponsive During ONTAP Upgrade on ASA-A30

Views:
9
Visibility:
Public
Votes:
0
Category:
asa-r2
Specialty:
hw
Last Updated:

Applies to

  • NetApp ASA-A30
  • ONTAP upgrade from 9.16P3 to 9.17P7

Issue

After upgrading ONTAP from 9.16P3 to 9.17P7, one controller (Node-01) became unresponsive and was not accessible via Service Processor (SP) or serial console. The system showed no BIOS or POST (Power-On Self Test) activity, and the following log entries were observed:

[Node-01:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e4a on node Node-01 has gone down unexpectedly.
[Node-01:vifmgr.clus.linkdown:EMERGENCY]: The cluster port e4b on node Node-01 has gone down unexpectedly.
[Node-01:monitor.globalStatus.critical:EMERGENCY]: This node has taken over Node-02.
[Node-01:monitor.globalStatus.critical:EMERGENCY]: Controller failover of Node-02 is not possible: version mismatch.

Symptoms:

  • No output on console or SP after upgrade.
  • Controller does not reach loader prompt.
  • BMC responds to power on/off but BIOS does not start.
  • System is not in production, no user impact at the time.

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.