Description |
This article describes an issue where, when an administrator analyzes traffic, no UUID is seen in the traffic log. |
Scope | FortiGate. |
Solution |
Occasionally, no UUID is seen in the traffic log when traffic is allowed by a forward traffic policy.
date=2023-07-31 time=12:35:09 eventtime=1690832109350004072 tz="-0700" logid="0000000013" type="traffic" subtype="forward" level="notice" vd="root" srcip=192.168.221.2 srcport=49679 srcintf="mgmt" srcintfrole="lan" dstip=192.168.198.2 dstport=22 dstintf="port2" dstintfrole="undefined" srccountry="Reserved" dstcountry="Reserved" sessionid=7144 proto=6 action="server-rst" policyid=3 policytype="policy" poluuid="0c2ca970-2fd9-51ee-15ae-a5d0fffd8ffc" policyname="Test" service="SSH" trandisp="noop" duration=5 sentbyte=48 rcvdbyte=40 sentpkt=1 rcvdpkt=1 appcat="unscanned"
There are two types of local in policy. For a customized local in policy, there is a UUID. For a default local in policy, there is no UUID. Use the CLI to check the default local in policy:
diagnose firewall iprope list
There is no UUID in the default local in policy. |