Skip to main content
NetApp Knowledge Base

Troubleshooting Node down and unresponsive via console or Service Processor

Views:
10,308
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
HW
Last Updated:

Issue

  • Node fails, which may or may not be taken over by partner.
  • Node fails to boot and serial console connection may yield no output.
  • Connection via SP/BMC may also fail.
    • Terminal screen is blank 
  • Physical inspection may show the controller has no lit LEDs and appears powered off despite connections to known good power.
  • Powercycle of SP/BMC or node does not fix the issue. - How to use the SP or BMC to non-disruptively powercycle a node
  • Attempt to connect to SP or BMC (which may or may not be accessible) and gather logs:
  • If SP/BMC is unresponsive over SSH, connect to console port with serial cable and hit Enter to determine if console is responsive/at LOADER.
  • If there is no output, attempt to toggle to SP/BMC with CTRL+G from a serial console connection and collect the same log output as above.

Note: To exit back to the console from the SP/BMC, use CTRL+D. For A700s systems, use Esc+T to return to the console instead.

  • Once logs have been collected or deemed impossible to collect, Reseat the controller (unseat from midplane, leave out for 1-2 minutes, seat back in place)

 

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.