Varonis DatAdvantage does not receive new audit events and Varonis FPolicy is disabled in the SVM [kern_audit:info:2041] 8503e800001089e7 :: Node01:ontapi :: 10.100.100.180:59222 :: SVM01:Domain\Servi...Varonis DatAdvantage does not receive new audit events and Varonis FPolicy is disabled in the SVM [kern_audit:info:2041] 8503e800001089e7 :: Node01:ontapi :: 10.100.100.180:59222 :: SVM01:Domain\Service-Varonis :: <netapp nmsdk_language="C" nmsdk_platform="Windows Server 2016 Standard AMD64" version="1.15" xmlns="http://www.netapp.com/filer/admin" nmsdk_version="5.3.1"><fpolicy-disable-policy><policy-name>Varonis</policy-name></fpolicy-disable-policy></netapp> :: Pending:
Applies to ONTAP 9 FPolicy Varonis Issue Varonis fails to enumerate shares with the following error: Error scanning shares: Error code -2147024843 The network path was not found. Enumerate share faile...Applies to ONTAP 9 FPolicy Varonis Issue Varonis fails to enumerate shares with the following error: Error scanning shares: Error code -2147024843 The network path was not found. Enumerate share failed Failed to call NetShareEnum. Verify target server is accessible and the user has the Power User and Backup Operator permissions.
Applies to FPolicy implementations including Varonis (and other Fpolicy vendors like Veritas Enterprise Vault, Quest,etc -however, this KB is specifically for Varonis) ONTAP 9+ Issue FPolicy is automa...Applies to FPolicy implementations including Varonis (and other Fpolicy vendors like Veritas Enterprise Vault, Quest,etc -however, this KB is specifically for Varonis) ONTAP 9+ Issue FPolicy is automatically re-enabled without direct user interaction This occurs despite an administrator issuing the following command to disable FPolicy ontap::> vserver fpolicy disable -vserver <vserver> -policy-name <policyname>
Applies to ONTAP 9.5 and later Varonis Filewalk Issue During attempt to Filewalk Varonis fails to enumerate shares when the LIF it is accessing does not allow CIFS and management access
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 brok...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 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 brok...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.' ).
A large number of FPolicy Policies can cause a timing problem in internal ONTAP tables that causes some policies to be in a disconnected state. In normal situations, Varonis sends a request to enable ...A large number of FPolicy Policies can cause a timing problem in internal ONTAP tables that causes some policies to be in a disconnected state. In normal situations, Varonis sends a request to enable the policy to the Vservers . When a policy is enabled, it also automatically triggers an engine-connect, the Vservers will reach out on port 2002 to establish the FPolicy session.
fpolicy: fpolicy.server.connectError:error]: Node failed to establish a connection with the FPolicy server "10.10.10.10" of policy "Varonis" for Vserver VS1 (reason: "TCP Connection to FPolicy server ...fpolicy: fpolicy.server.connectError:error]: Node failed to establish a connection with the FPolicy server "10.10.10.10" of policy "Varonis" for Vserver VS1 (reason: "TCP Connection to FPolicy server failed."). Fpolicy-mlog-txt.gz errors show that ONTAP tries to connect to primary and secondary fpolicy servers, but can't establish TCP connection. After the TCP connection is closed, the FPolicy server tries again to establish a TCP connection.