Troubleshooting Node down and unresponsive via console or Service Processor
Applies to
- AFF systems
- FAS systems
- Service Processor (SP)
- Baseboard Management Controller (BMC)
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
Enterto determine if console is responsive/atLOADER. - If there is no output, attempt to toggle to SP/BMC with
CTRL+Gfrom 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)
