Skip to main content
NetApp Knowledge Base

During ONTAP upgrade cluster network ports are down

Views:
2,903
Visibility:
Public
Votes:
1
Category:
fas-systems
Specialty:
HW
Last Updated:
3/13/2025, 12:22:26 PM

Applies to

  • FAS2720
  • FAS2750
  • FAS8200
  • AFF A220
  • AFF C190
  • ONTAP upgrade
  • Switchless cluster

Issue

  • One of the nodes completes the update and reboots just running its root aggregate.
  • The node reports waiting for cluster applications to come online:

CLI::> storage failover show
                              Takeover
Node           Partner        Possible State Description
-------------- -------------- -------- -------------------------------------
cluster1-01
               cluster1-  true     Connected to cluster1-02
               02
cluster1-02
               cluster1-  true     Connected to cluster1-01.
               01                      Waiting for cluster applications to
                                       come online on the local node.
                                       Offline applications: vldb, vifmgr,
                                       bcomd, crs, scsi blade, clam.
2 entries were displayed.

  • Partner node is still running the previous ONTAP version in a Partial Giveback status.
  • On each node, the cluster network ports are down:

CLI::*> network port show
Node: node_name_01
                                                  Speed(Mbps) Health   Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status   Status
--------- ------------ ---------------- ---- ---- ----------- -------- ------
...
e0a       Cluster      -                down 9000  auto/auto  -        false
e0b       Cluster      -                down 9000  auto/auto  -        false
...
10 entries were displayed.

  • Automated Non-Disruptive Update (ANDU) is paused:

[node_name_02: upgrademgr: upgrademgr.update.pausedErr:error]: The automated update of the cluster has been paused due to the following reason:  Node "node_name_01": Error: {Node "node_name-02" is not in "connected" state after giveback.}, Action: {Use the "storage failover show" command to verify that node "node_name-02" is in the "connected" 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.