Skip to main content
NetApp Knowledge Base

CONTAP-392355: ONTAP FPolicy configuration replay fails after node reboot or upgrade

  1. Last updated
  2. Save as PDF
Views:
1,235
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
NAS
Last Updated:

Issue

  • FPolicy configuration replay fails after a node reboot or ONTAP upgrade
  • The following errors appear repeatedly in the FPolicy log:

    [kern_fpolicy:error:9887] No Vserver Configured...
    [kern_fpolicy:error:9887] Populate ScreenReq failed with error = 3. Setting nblade response to ALLOW

  • The following event is logged on the affected node:

    mgmt.fpolicy.replay.failed: FPolicy configuration replication process failed.

  • FPolicy Service Manager process exits repeatedly and attempts to restart:

    spm.fpolicy.process.exit: Fpolicy Service Manager process with ID <pid> exited as a result of signal signal 15. The service will attempt to restart.

  • vserver fpolicy show-engine may return an RPC error on the affected node:

    Warning: Unable to list entries on node <node>. RPC: Remote system error [from mgwd on node "<node>" (VSID: -1) to fpolicy at <address>]

  • FPolicy nblade configuration cache becomes out of sync with the mirror tables following the failed replay

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.