Skip to main content
NetApp Knowledge Base

Varonis FPolicy disconnecting repeatedly due to Varonis engine not listening properly to it's configured port

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

​ ​

Applies to

ONTAP 9

Issue

  • Frequent EMS/Event log entry sequence:

Mon Jan 04 12:09:45 EST [example: fpolicy: fpolicy.server.connectError:error]: Node failed to establish a connection with the FPolicy server '10.1.1.101' (reason: 'Connection to FPolicy server is broken(EPIPE) received.').
Mon Jan 04 12:09:45 EST [example: fpolicy: fpolicy.server.disconnect:warning]: Connection to the Fpolicy server '10.1.1.101' is broken ( reason: 'FPolicy server is removed from external engine.' ).
Mon Jan 04 13:06:11 EST [example: fpolicy: fpolicy.server.disconnect:warning]: Connection to the Fpolicy server '10.1.1.101' is broken ( reason: 'FPolicy server is removed from external engine.' ).
Mon Jan 04 13:06:36 EST [example: fpolicy: fpolicy.server.connectError:error]: Node failed to establish a connection with the FPolicy server '10.1.1.101' (reason: 'Select Timed out.').

  • Packet traces between Fpolicy server and SVM confirm: Fpolicy server is abruptly terminating TCP connections.
  • Varonis is listening on port 2002 on the FPolicy server
C:\> netstat -an

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2002           0.0.0.0:0              LISTENING

 

 

 

 

 

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.