Hot!session clash log

Author
jiwon kang
New Member
  • Total Posts : 1
  • Scores: 0
  • Reward points: 0
  • Joined: 2020/07/20 18:11:19
  • Status: offline
2020/07/20 18:20:30 (permalink) 5.6
0

session clash log

hi, 
 
Please tell me why the log occurred and how to take action.
I am using forti-OS 5.6.8
 
07 | 20 | "0100020085" | session clash" new_status="state=00010404 tuple-num=2 policyid=107 identidx=0 dir=0 act=2 hook=0 1.226.64.90:43443->172.25.5.234:5911(218.146.32.6:10329)
dir=1 act=1 hook=4 218.146.32.6:10329->1.226.64.90:43443(172.25.5.234:5911)" old_status="state=00010404 tuple-num=2 policyid=107 identidx=0 dir=0 act=2 hook=0
1.226.64.90:43443->172.25.5.234:5909(218.146.32.6:10329) dir=1 act=1 hook=4 218.146.32.6:10329->1.226.64.90:43443(172.25.5.234:5909)
 
thanks
#1

1 Reply Related Threads

    Yurisk
    Bronze Member
    • Total Posts : 47
    • Scores: 10
    • Reward points: 0
    • Joined: 2011/12/04 03:30:01
    • Status: offline
    Re: session clash log 2020/07/20 23:52:29 (permalink)
    0
    "Session clash messages appear in the logs when a new session is created but a conflicting similar session already exists."  https://kb.fortinet.com/kb/documentLink.do?externalID=FD37215
    Usually happens while doing NAT of some sort Fortigate runs out of the free/available ports to do the translation for the new arriving connection. 
    #2
    Jump to:
    © 2020 APG vNext Commercial Version 5.5