Skip to main content
NetApp Knowledge Base

SP firmware doesn't update to version bundled with ONTAP after upgrade

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

Applies to

  • AFF A300
  • After upgrading ONTAP from 9.13.1P16 to 9.16.1P4
  • Service Processor (SP) 5.9 and later

Issue

  • After upgrading ONTAP from 9.13.1P16 to 9.16.1P4, the Service Processor (SP) firmware on one node doesn’t update to the version bundled with the new ONTAP image 5.11P3.
  • system service-processor image update-progress show indicates 0% progress for the affected node.

 

Cluster::*> system service-processor image update-progress show
                 In                           Percent
Node             Progress Start Time          Done    End Time
---------------- -------- ------------------- ------- -------------------
node-01  no       - 0       -
node-02  no       10/20/2025 15:58:50 100     10/20/2025 16:03:15
2 entries were displayed.

  • EMS logs show following errors.

[node-01:rlm_hbtrcv_non_blocking:spmgmt.driver.timeout:error]: The software driver for the Service Processor (SP) detected a problem: Unable to update SP network information at this time.

[node-01:servprocd:sp.firmware.incompatible:alert]: The SP firmware version 5.11 is not compatible with this version of Data ONTAP.

  • sysconfig -a confirm the SP firmware remained at 5.11 instead of updating to 5.11P3.
  • The partner node updated the SP firmware successfully.
  • Since it is SP version 5.9 or later, bug CFBMC-762 has already been fixed in this version.

 

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.