Skip to main content
NetApp Knowledge Base

Node failed to establish a connection with the FPolicy server (reason: "Select Timed out.") because Collector Name is wrong

Last Updated:

Applies to

  • ONTAP 9
  • Fpolicy
  • Varonis


  • Fpolicy server is not recieving events from ONTAP
  • EMS repeatedly says
    • Thu Mar 07 12:43:36 -0500 [node-08: fpolicy: fpolicy.server.disconnect:error]: Connection to the FPolicy server "x.x.x.x" of policy "policy_name" is broken for Vserver svm_name ( reason: "FPolicy server is removed from external engine." ).
      Thu Mar 07 12:44:29 -0500 [node-08: fpolicy: fpolicy.server.connectError:error]: Node failed to establish a connection with the FPolicy server "x.x.x.x" of policy "policy_name" for Vserver svm_name (reason: "Select Timed out.").
  • Varonis Fpolicy log says

    • Error description: Failed to connect to file server svm_name. Error reason: Wait for connection timed out. Possible solutions: Ensure the 'policy_name' FPolicy primary servers, port and authentication type are correct and the server is not experiencing high load. Detailed info: Failed to connect to server svm_name, NetappCM did not initiate connection with forwarder within 30000 milliseconds.
  • Dual packet traces show that the Fpolicy server is receiving TCP SYN packets sent from ONTAP, but is not responding.

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.