Skip to main content
NetApp Knowledge Base

FPolicy event isn't generated in a node along with "TCP Connection to FPolicy server failed" in EMS

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

Applies to

  • ONTAP 9
  • FPolicy

Issue

  • FPolicy event resulted from client access is not generated on one volume on a node
  • EMS event for fpolicy.server.connectError stating that the TCP Connection to the FPolicy server failed:
Wed May 27 16:02:19 CEST [cluster-01: fpolicy: fpolicy.server.connectError:error]: Node failed to establish a connection with the FPolicy server "10.1.1.100" (reason: "TCP Connection to FPolicy server failed.").

 

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.