Hot!FortiOS 6.2: memory issues, best approach

Author
ted barker
Bronze Member
  • Total Posts : 36
  • Scores: 0
  • Reward points: 0
  • Joined: 2016/10/26 14:43:11
  • Status: offline
2019/04/01 12:29:48 (permalink)
0

FortiOS 6.2: memory issues, best approach

Hi, 
 
I've been running 6.2 Beta and have switched to 6.2 public release, but the memory goes quickly up and system enters conserve mode and the system becomes unusable.
 
The 61E was running always around 75 to 80% for a couple of months, now with 6.2 the memory increased after an hour to that level and became useless.
 
What are your experiences and any best approaches with 6.2 troubleshooting (most probably the same as before) and feedback to Fortinet?
#1

5 Replies Related Threads

    seadave
    Platinum Member
    • Total Posts : 315
    • Scores: 45
    • Reward points: 0
    • Joined: 2004/11/03 18:02:09
    • Location: Seattle, WA
    • Status: offline
    Re: FortiOS 6.2: memory issues, best approach 2019/04/01 16:32:10 (permalink)
    0
    .0 releases of FortiOS are notorious for having bugs.  If this is a testing/lab firewall then go for it, but if you are using this in a production environment you are better off using a later 5.6.X or 6.0.X release for stability. 
     
    For example at work we are still on a later variant of 5.6.X for a 500D supporting hundreds of users, while at home I have a FWF60E and I'm running 6.0.3.  I had some issues with DNS and 6.0.4 so I haven't gone past .3 yet.
     
    We just grabbed a pair of 501s, and we will test 6.0.4 on those before we put into production with the assumption that the newer hardware on the 501Es will handle 6.0.X better.
     
    I know it is tempting to get access to the latest gizmos, but on a FG of your size you are going to be constrained as to what you can do.  It may help to review the features enabled and turn off anything you are not using such as WLAN or Switch Control, Adv Routing, etc.
     
    If you do open a ticket, you can SSH into the gate and capture some of the following:
     
    diag debug crashlog read
    (If that is insanely long, use "diag debug crashlog clear", wait 24 hours and send the new output)
    If the UI is crashing and you can login, you may need to keep an open terminal session up via serial to capture the output, or enable Syslog.
     
    Here is an article with more info:
     
    https://help.fortinet.com/fos50hlp/54/Content/FortiOS/fortigate-toubleshooting-54/troubleshooting_tools.htm
     
    for 5.4 but still useful.
     
     
    #2
    seadave
    Platinum Member
    • Total Posts : 315
    • Scores: 45
    • Reward points: 0
    • Joined: 2004/11/03 18:02:09
    • Location: Seattle, WA
    • Status: offline
    Re: FortiOS 6.2: memory issues, best approach 2019/04/01 16:34:44 (permalink)
    0
    You should follow/read this thread also: https://forum.fortinet.com/tm.aspx?m=172872
     
    #3
    sullimd
    New Member
    • Total Posts : 3
    • Scores: 0
    • Reward points: 0
    • Joined: 2015/08/17 09:11:55
    • Status: offline
    Re: FortiOS 6.2: memory issues, best approach 2019/07/09 23:06:00 (permalink)
    0
    Experienced the same thing with 2 customers - today.  It's the wad service using all the memory, device goes into conserve mode, then I get a call that the internet is down.
     
    #diag sys top - find the wad service
    #diag sys kill 11 wad-service-id
    #4
    BrianB
    New Member
    • Total Posts : 9
    • Scores: 0
    • Reward points: 0
    • Status: offline
    Re: FortiOS 6.2: memory issues, best approach 2019/07/10 08:59:25 (permalink)
    0
    Two 1500D's in HA A/P
    WAD service creates memory creep.
    Created an automation stitch to restart the WAD process daily at 3am.  Supposedly fixed in 6.2.1
    Once restarted memory drops by 20%.
     
    diagnose test application wad 99
    #5
    mok
    New Member
    • Total Posts : 8
    • Scores: 0
    • Reward points: 0
    • Joined: 2016/01/28 06:50:01
    • Status: offline
    Re: FortiOS 6.2: memory issues, best approach 2019/07/15 01:23:35 (permalink)
    0
    Anyone know when the 6.2.1 will be release ?!
    3 month with this bug, it is very annoying.
    #6
    Jump to:
    © 2019 APG vNext Commercial Version 5.5