Skip to main content

This Site will be down for up to 3 hours on December 2, 2023 from 8 PM - 11 PM PST, to deploy an infrastructure update.

NetApp Knowledge Base

Why did my SP/BMC reboot during a FW upgrade?

  1. Last updated
  2. Save as PDF
Views:
477
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • All Platforms
    • ASA systems
    • AFF systems
    • FAS systems

Answer

After the SP/BMC update is complete, the SP/BMC is automatically rebooted. You do not need to trigger an SP/BMC reboot manually.

  • This is expected behavior.

Firmware update will need to reboot the SP on completion. If your console connection is through the SP, it will be disconnected.

  • To display the SP/BMC update status, including whether an update is in progress, the update start and end time, and the completion percentage:
system service-processor image update-progress show -node node1
 
 
Node: node1
Latest SP Firmware Update Start Timestamp: 7/18/2017 12:22:37
Latest SP Firmware Update Percentage Done: 100
Latest SP Firmware Update End Timestamp: 7/18/2017 12:28:14
Is Update in Progress: no
 
  • Verify that the SP/BMC is online and running the intended version:

system service-processor show -node node1

Additional Information

  • This is covered on mysupport.NetApp.com Downloads >Firmware> System Firmware & Diagnostics
  • The download page will provide the steps to update your SP/BMC

 

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.
Scan to view the article on your device