Skip to main content
NetApp Knowledge Base

ACP module stuck in "rebooting" state after ACP firmware upgrade from 02.10 to 02.12

Last Updated:

Applies to

  • In-Band Alternate Control Path (ACP)
  • IOM6 module
  • ACP firmware upgrade from 02.10 to 02.12
  • FAS/ AFF Platforms
  • ONTAP 9


  • Either one or both the nodes in an HA pair reporting few ACP modules in “rebooting” state 

Cluster::*> storage shelf acp module show
Node               Module Name        State
-----------------  ------------       -------------      
Node-N1            6.20.A             rebooting
                   5.10.A             active
                   6.20.B             rebooting
                   5.10.B             active
Node-N2            6.20.A             rebooting
                   5.10.A             active
                   6.20.B             rebooting
                   5.10.B             active

  • The ACP firmware was upgraded from 02.10 to 02.12 as part of ONTAP upgrade or manually upgraded
  • The output of acpadmin ibacp_list_all shows ACP module Current State as 0x17 and firmware as

Cluster::> node run -node Node-N1 acpadmin ibacp_list_all
Number of ACP modules 4
MAC                SES    Last Contact  Protocol   Assigner    Shelf             Current Inband   IOM     shelf
Address            bit    (seconds ago) Version    ACPA ID     S/N               State   ID       Type    flag
00:a0:98:XX:XX:XX  01      23161715   0         SHJHU171XXXXXXX   0x17   0d.20.A  IOM6     0x20
00:a0:98:XX:XX:XX  01      428    0         SHJHU171XXXXXXX   0xd    0d.10.A  IOM6     0x20
00:a0:98:XX:XX:XX  01      23132624   0         SHJHU171XXXXXXX   0x17   0b.20.B  IOM6     0x20
00:a0:98:XX:XX:XX  01      23126011   0         SHJHU171XXXXXXX   0xd    0d.10.B  IOM6     0x20

  • Soft power cycle of affected ACP module didn't make any change in the state of module


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.