Skip to main content
Paul_S
Paul_S
New Member
August 23, 2016
Solved

FGT60E 5.4.1 not showing forward traffic logs and forticloud issue

  • August 23, 2016
  • 1 reply
  • 62755 views

using standalone FG60E v5.4.1, logging to memory and forticloud (if I can get it working).

 

forward traffic logs are blank. I tried UTM events, all session and web profile "log-all-urls". log still blank.

 

also the forticloud test account button does not work and the account box is blank, but cannot be changed.

    Best answer by Justfly

    Hi,

    I had the same problem.

    Use the following commands to show allowed traffic in memory log.

     

    config log memory filter set severity information end

     

    Regards,

    Justfly

     

    1 reply

    awasfi_FTNT
    Staff
    awasfi_FTNT
    Staff
    August 23, 2016

    Hello,

     

    Check the following:

    config  log  memory filter

    get                               <<-- list all options

    Make sure forward-traffic logs enabled. If not then:

    set forward-traffic enable

    end

     

    The same for FortiCloud:

    config  log  fortiguard filter

    set forward-traffic enable

    end

     

    Enable "Log Allowed Traffic" and select "All Sessions" on the firewall policy.

     

    Make sure you display logs from the correct location(GUI):

    "Log & Report >> Log Settings >> GUI Preferences >> Memory/FortiCloud"

     

    FortiCloud you need to register the account first before using it (It's different than the account used for support portal). Under "Dashboard >> License Information" locate FortiCloud and register it then it should be available.

     

    Regards,

     

    Paul_S
    Paul_SAuthor
    New Member
    August 23, 2016

    I will do this. I like the CLI, but many of my colleagues do not.

     

    Is there a way in the GUI to do this?

    awasfi_FTNT
    Staff
    awasfi_FTNT
    Staff
    August 24, 2016

    Hello,

     

    Not every option available from CLI, however forward-traffic should be enabled by default.

    It looks like the issue is the GUI location where you displaying the logs from.

     

    Regards,

    Terms & ConditionsAccessibility statement