Skip to main content
NetApp Knowledge Base

Fpolicy FSM Panics after upgrading to ONTAP 9.13.1 when using schema version 3

Last Updated:

Applies to

  • Fpolicy
  • ONTAP 9.13.1
  • Cryptospike


9.13.1 introduced fpolicy protocol version 3. Performing FPolicy protocol handshake with version 3.0 might lead to issues with EMS errors below:
[?] Wed Jun 28 18:29:27  0000 [netapp2-01: fpolicy: fpolicy.server.connect:notice]: Control channel with the FPolicy server "" of policy "cs_release_policy_cifs" is established for Vserver svm1.
[?] Wed Jun 28 18:29:27  0000 [netapp2-01: fpolicy: ucore.panicString:error]: 'fpolicy: assertion (0) at src/fsm/ failed, raising SIGABRT(6) at RIP 0x8051f968a (pid 28798, uid 0, timestamp 1687976967)'

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.


  • Was this article helpful?