Skip to main content
Nicolas_Marengo
New Member
August 15, 2013
Question

Antivirus change from Proxy-based to Flow-Based

My cluster of 2 x Fortigate 60C hits 100% very very often. One of the many changes im doing is reducing the amount of logging and UTM being done and apply them to traffic a bit more specific. I have also change most of the utm from proxy to flow-based. But when trying to change the Antivirus, it says: Value conflicts with system settings. I cannot find the system settings anywhere... Anyone can help? Thanks Nico

    8 replies

    Nicolas_Marengo
    New Member
    August 15, 2013
    .... So when trying to do the same change over CLI, the error is more descriptive. ========== fgt60c_ha_1 (default) # set inspection-mode flow-based failed! profile used by policy settings! node_check_object fail! for inspection-mode flow-based value parse error before ' flow-based' Command fail. Return code -7 ========== After removing the antivirus from ALL the policies i can now change it to flow-based. Thing is... is not being applied to any policy now until i re-add it.... Pain in the a$$
    Nicolas_Marengo
    New Member
    August 15, 2013
    Having said that.. it cannot be added back into the policies. So im not sure what the expected behavior is for this.
    ssu_FTNT
    Staff
    Staff
    September 4, 2013
    Due to limited storage space, 60C support proxy or flow mode but not at same time. In my practice, if you want to change from proxy to flow: 1. Make sure all vdom all policy do not have av profile. 2. Change av default-db setting to normal 3. Change or create new av profile in flow mode 4. Do a manually db update by exe update-now 5. Apply av profile to policy again, and you are good to go
    Sean_Toomey_FTNT
    Staff
    Staff
    August 6, 2014
    I would update to version 5.2 as there are major improvements to flow UTM since 5.0 Ensure that all of your UTM protections are in flow.. IPS and AppCtrl just use IPS engine, but Email Filtering, Web Filtering, Antivirus, DLP, these all need to be in flow mode. If any are proxy mode you will end up using the proxy again. Hope that helps. Cheers!
    Istvan_Takacs_FTNT
    Staff
    Staff
    August 7, 2014
    Hi Nicholas, 60Cs also don' t have built-in CPs/SPs (FortiASIC content/security processor) to off-load scanning from the main CPU. If you want to stay on the safe side and protect your network from nasty viruses, but also to have proper performance at the same time, it might be the time to upgrade to a device that can handle both scanning and other firewall duties at the same time. The smallest device that comes with a dedicated CP8 processor is the Fortigate 100D. If you follow all the previous advices and you still are having issue with the load, than it might only be the matter of having such a huge traffic passing through your cluster that the hardware can' t handle it anymore and time to look into the upgrade option. 100Ds also come with dual core CPU which would help with other traffic processing, too
    Mika
    New Member
    August 11, 2014
    Also, which version are you running? There might be some improvements in the latest FortiOS
    dasilva13
    New Member
    August 12, 2014
    I will have to agree with Istvan, I have many 60C out in the field, and the 100d, with dedicated processor handles UTM MUCH MUCH better in my opinion. We are hit and miss with the lower end models and always try to push at least the 100d model.
    sebastan_bach
    New Member
    December 8, 2015

    I hope FG should document the device models with the CP version that comes with the device. 

     

    Regards

     

    Sebastan

    Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
    Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
    Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT