Hot!Pings from CLI not seen in Logs&Reports or Fortiview

Author
vlw38
New Member
  • Total Posts : 8
  • Scores: 0
  • Reward points: 0
  • Joined: 2020/04/03 11:09:12
  • Status: offline
2020/06/18 13:08:53 (permalink)
0

Pings from CLI not seen in Logs&Reports or Fortiview

Pings from Fortigate CLI out to internet or to internal hosts are  not seen in Logs&Reports or in Fortiview.
Is this expected behavior?  I have Event Log/Local Log = all in Log Settings and Log= All in specific IPV4 policy rules.
#1

2 Replies Related Threads

    lobstercreed
    Gold Member
    • Total Posts : 251
    • Scores: 32
    • Reward points: 0
    • Joined: 2018/11/28 14:57:58
    • Location: Sedalia, MO
    • Status: offline
    Re: Pings from CLI not seen in Logs&Reports or Fortiview 2020/06/18 13:49:32 (permalink)
    0
    Yes, the traffic is not hitting any policies since it is not ingressing one interface and egressing another.  Generally you are doing this for testing so not really sure why you'd need it logged?
    #2
    vlw38
    New Member
    • Total Posts : 8
    • Scores: 0
    • Reward points: 0
    • Joined: 2020/04/03 11:09:12
    • Status: offline
    Re: Pings from CLI not seen in Logs&Reports or Fortiview 2020/06/18 14:26:08 (permalink)
    0
    Good point re: ping traffic not ingressing/egressing interface.  And yes I am doing failover testing and wanted confirmation of the destination interface used by my test pings. But now I understand why I won't be able to see/log that info. Sounds like I should run my test pings from a device other than the fortigate and make sure I have a policy to match that traffic. Thanks much!
    #3
    Jump to:
    © 2020 APG vNext Commercial Version 5.5