Skip to main content
NetApp Knowledge Base

CONTAP-229226: Slow response to API calls on the takeover/surviving node while the partner node was stuck and failed to reboot

  1. Last updated
    May 6, 2025
  2. Save as PDF
Views:
39
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
cloud
Last Updated:
5/6/2025, 2:06:58 PM

Issue

  • One node (Node 1) took over the other node (Node 2)
  • Node 2 was not accessible through SSH or REST API calls though node 1 saw it was still up
  • Node 1, the takeover/surviving node, continued to serve user data
  • Node 1 was slow to SSH and REST API calls, resulting in health check timeout/failures by FSx Control Plane
  • Node 2 had to be restarted/NMI’ed from AWS Console or CLI to recover

 

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.