Skip to main content
Best answer by Jordan_Thompson_FTNT

Raudi wrote:

Yesterday i had a issue with 6.4.1 too, after 24 days in my homeoffice my internet access was gone, so i logged in to the 100E and the device shows "conserve mode".

 

I made a litte research and all the memory was used by "480" tasks with the name "node".

 

Now after a reboot the memory usage is going slowly straight up, so i think in a few days i must reboot the device again. At the moment i have 186 of the "node" tasks, and every few minutes i can count one more...

 

Thanks for the report. We are working on a fix for this issue for 6.4.2.

7 replies

bamather
bamather
New Member
June 5, 2020

I have not, but about to upgrade in my lab setup this weekend.  Currently running 6.4.0 and so far have been impressed but still really buggy.  Hope 6.4.1 will be good as we are suffering many bugs from the 6.2 train in our production environment.  

tanr
tanr
New Member
June 5, 2020

The list of Known Issues is very small, but that's not all that reassuring for a .1 release. 

bamather
bamather
New Member
June 5, 2020

I'm sure more will be added as more people roll it out.  Will let you guys know how the update went this weekend.

brycemd
brycemd
New Member
June 5, 2020

What's with the lack of support for the F series? F series wasn't a part of the beta, it did have a 6.4.0 release, and now it's not even on the supported models for 6.4.1

Belgarioz
Belgarioz
Visitor III
June 7, 2020

Me.

There are some issue solved: like ssl vpn split tunnel not working an MacOS computers.

 

But there are some glitches (probabily) grafical not working. Right now i am unable to set up a a fabric device 'cause the page seems "broken".

seadave
seadave
New Member
June 9, 2020

NOTE: I manage two 501Es HA in production.  I will NOT be updating those for a bit longer.  This was done on home/lab equipment.  Don't be careless at work with firmware this new!!! So I took the plunge.  My home setup is a FWF-60E, connected to a FSW108DPoE, that hosts a FortiAP 221C.  I was running 6.0.9.  It has been ok, but has randomly stopped working every two or three months requiring a reboot.  I've never taken the time to find root cause. I realized that Device ID and Tags will be removed or modified due to the update.  I use free FortiCloud logging as FAZ is too expensive for home use (unfortunately). I updated to 6.2.4 first.  No problems.  The process converted my custom Device IDs to type Device (MAC Address).  Each device was renamed in the following format: _upg_dev_DEVICENAME@XX:XX:XX:XX:XX:XX So, nice that FTNT embed that info in the name.  If  you use Device IDs heavily, make sure you read the release notes and understand how this will work. My FortiSwitch and FortiAP were detected and manageable without error as far as I could tell.  I have a very simple setup (two VLANs) though so YMMV. I next upgraded to 6.4.0 again no problems.  Some menus seems snappier and I like the UI.  I let it stabilize for about 10 minutes and then went on to 6.4.1. After the update regarding 6.4.1 you are presented with a screen that looks like the config may have defaulted.  It doesn't.  It is only asking you if you'd like to optimize the dashboard widgets.  Select Optimal and OK (unless you want to keep your old layout).  You are then shown a screen asking if you'd like to review new features.  After dismissing that, you are in the GUI. If you check the available widgets, there are a ton of options now. So it seems like things are working ok.  Will update if I see any oddness or other stability issues.  Memory is running at 50% which is less than when I was running 6.0.9 so that is nice.

 

Edit: After 48 hours things are still running fine.  I was able to add a second SSID for a project and that was easy.  FWF60E is consuming on average 66% of RAM with ~20 IP devices, FortiSwitch and FortiAP controller enabled.  SLL Inspection isn't being used and VPN is not either.  Policies are using IPS/IDS, Webfilter, AV, and App Control.

 

So far so good.

aagrafi
aagrafi
New Member
June 13, 2020

No time for debugging...

neonbit
neonbit
New Member
June 14, 2020

Note a big change with 6.4.1 is that SDWAN interfaces are now added into zones. I upgraded from 6.4.0 and the interface zones got created automatically.

 

It's a cool feature as you can now just reference the SDWAN zones in your policies.

 

Still waiting for FMG 6.4.1 before I upgrade my main devices.

Magnitude_8
Magnitude_8
Explorer
June 25, 2020

I've just updated my first FortiGate from 6.4.0 to 6.4.1. Initial testing looks good. Feels like this should have been the 6.4.0 release. New dashboards replace FortiView and the GUI just seems much faster.

 

Only issue I have found so far is they way SD-WAN is upgraded to SD-WAN Zones. Rather than upgrading the old SD-WAN interface to an SD-WAN Zone, member interfaces are added to separate SD-WAN Zones (virtual-wan-link and upg-zone-wan1 in my case).

 

This means that the old SD-WAN interface have been replaced with two zones in all policies and Interface Pair View can no longer be activated.

 

I assume I can just move the secondary interface to the virtual-wan-link zone and delete upg-zone-wan1 from all the rules, but am not certain. Also, the default route is still SD-WAN, so I'm not clear how traffic is now being routed.

 

In general, this looks like a good update, but I wish Fortinet had provided a bit more guidance around SD-WAN. I'll post again if I experience any issues.

thuynh_FTNT
Staff
thuynh_FTNT
Staff
July 6, 2020

>Only issue I have found so far is they way SD-WAN is upgraded to SD-WAN Zones. Rather than upgrading the old SD-WAN interface to an SD-WAN Zone, member interfaces are added to separate SD-WAN Zones (virtual-wan-link and upg-zone-wan1 in my case). Hi there, did you use individual SD WAN member in firewall policy before the upgrade? If so, firmware upgrade will detect that and auto-create an "upg-zone-xxx" SD WAN zone for that member interface and move it there. If not, all SD WAN members should stay in a default "virtual-wan-link" zone. Let me know if that's not the case. If so, please send me your related SD WAN config.

owla
owla
New Member
July 7, 2020

Double post

owla
owla
New Member
July 7, 2020

We had one more issue with 6.4.1 

All firewall policies with Flow-based Inspection mode had a warning signs, You can not use inspection mode with current settings. We didn't find the cause of that messages (probably there are new requirements for flow-based mode)

There are not messages in [strike]6.4.2. [/strike] 6.2.4

 

seadave
seadave
New Member
July 8, 2020

owla wrote:

We had one more issue with 6.4.1 

All firewall policies with Flow-based Inspection mode had a warning signs, You can not use inspection mode with current settings. We didn't find the cause of that messages (probably there are new requirements for flow-based mode)

There are not messages in 6.4.2.

 

Do you mean 6.2.4?  I don't see 6.4.2 released unless you are beta testing?

seadave
seadave
New Member
July 8, 2020

One other point of note, is I assume you upgraded from 6.2.4 to 6.4.0 and then 6.4.1?  Going from 6.2.4 to 6.4.1 isn't supported if I recall.  I just took at 500D from 5.6.4 to 6.4.1 (going to 6.4.0 first was part of the process) and it is running fine, but we are only using it as a one arm sniffer without any other policies so the config is very simple.

 

JollyJohn
JollyJohn
New Member
July 9, 2020

@bommi I'm running v6.4.1 build1637 (GA) on two 60E-DSL units. One has 2x 128POE switches, the other has 1x AP221. So far so good. Everything came up, though I elected to config from scratch. The GUI is nicer and more responsive. After about a week the only issue I've really hit is about not being able to create address objects - just doesn't work through the GUI. Tonight I'll try CLI and see if I can figure out what's happening. 

Tomorrow I'll be adding 3 more APs and on Monday we get about 60 users starting. Fingers crossed!

Terms & ConditionsCookie settingsAccessibility statement