Netflow export with R80.30/R80.40

[TomShanti]

Hi community,

since R80.30 netflow export needs to be additionally configured on each rule via adding the "Accounting" option:

https://sc1.checkpoint.com/documents/R80.40/WebAdminGuides/EN/CP_R80.40_Gaia_AdminGuide/Content/Topi...

Could someone please share their experience regarding performance when enabling accounting ?

I remember some days in the past that the accounting option was very performance intense ...

And also how are we supposed to manage this with a 1000+ ruleset ?

Thanks and regards 

Thomas

[PhoneBoy]

The massive performance impact was back in the days before SecureXL, which handles this pretty efficiently. 
There is some extra logging traffic, as you might imagine.

[Oscar_Figueruel]

Dear Tom, we are suffering the same issues on our site.

Netflow stopped working since we upgraded and now we have to enable the accounting on thousands of rules , something that was not required at all in R80.10. this doesn't make any sense even when they are going to revert back this feature in R81, meaning that the accounting won't be required to get Netflow working.

Checkpoint, before performing these behaviour changes, you should think on the fact that these changes are causing a huge time consuming for your customers and not only this, but also the high performance impact it has on the MLMs.

[rdevarak · Accepted solution]

Thank you all for the feedback. Understood. In R81, the default behavior will be same as R80.10 and we are working to make a fix available in Jumbo HFs for R80.30/40 as soon as possible. Here is the silver line, now users can selectively choose FW rules for minimal impact on the performance or debugging purpose.

Due to architectural changes in R80.20, we had to make a hard decision regarding Netflow functionality.

[Tulasidhar_P]

We have netflow issue post upgradation to R80.40 but it is not related to enabling the Accounting option. We had R80.20 and Netflow is enabled with Loopback IP as Source IP and pushed the netflows in the VPN tunnel to Netflow collector which is at remote office. Upgraded to R80.40 since then the Netflows are not using the Loopback IP address as source rather they are trying to use the outgoing Interface IP address(Public IP in my case) as source IP address. removed and reconfigured but it did not work. tried configuring different collector pointing to the Local LAN with Loopback IP as Source IP still the Netflows using the outgoing Interface IP as source IP only. Any idea ?