Skip to main content
NetApp Knowledge Base

Takeover triggered by unexpected power loss in FAS8300 systems

Views:
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

FAS8300

Issue

  • Two unexpected system reboots were observed.
  • During the first reboot, the system recovered, and Giveback was successful.
  • During the first reboot, there is no obvious HW failure information or panic information in the BMC log.
  • The controller reported a simultaneous loss of DC power from both power supplies (PSU1 and PSU2), causing the node to reboot automatically and triggering a takeover.

BMC console log
Entity Presence PSU1_VIN_TYPE_DC | Absent | Asserted
Entity Presence PSU2_VIN_TYPE_DC | Absent | Asserted
System Firmware Progress | Secondary CPU Initialization | Asserted
System Firmware Progress | USB resource configuration | Asserted
System Firmware Progress | PCI resource configuration | Asserted
System Firmware Progress | Video initialization | Asserted
System Firmware Progress | Keyboard controller initialization | Asserted
System Firmware Progress | Hard-disk initialization | Asserted
System Firmware Progress | Hard-disk initialization | Asserted
System Event |  | Asserted

  • During the second reboot, system failed to power on even after power cycle (system power off/on).
  • System power status remained as "Host power is off" 
    Commands issued via BMC (e.g., system power on, system console) yielded no response.

BMC Log:

BMC > system power status
Host power is off
BMC > system power off
Current power is off, no action is taken
BMC  system power status
Host power is off
BMC > system power on
BMC > system console
 →Pressing the enter key gives no output.
BMC > system power status
Host power is off
BMC >

 

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.