v6.0 is here

[emnoc]

I hope it 's  all good  ;)

[romanr · Accepted solution]

Andy Bailey wrote:

I've getting a "Failed to save some changes: Input value is invalid" message (showing in the attachment) when I try and modify a policy (for example add an anti-spam to an existing policy).

Hey,

I don't have that problem - works fine for me since Beta 3.

Can you run the following on a Command Line, while you try to modify a policy:

diag deb reset

diag deb ena

diag deb cli 8

... and post the output

Br,

Roman

[Jordan_Thompson_FTNT · Accepted solution]

romanr wrote:

Andy Bailey wrote:

I've getting a "Failed to save some changes: Input value is invalid" message (showing in the attachment) when I try and modify a policy (for example add an anti-spam to an existing policy).

Can you run the following on a Command Line, while you try to modify a policy:

diag deb reset

diag deb ena

diag deb cli 8

... and post the output

In addition, please enable "diag debug app httpsd -1" and include that output.

[RobertReynolds]

https://docs.fortinet.com/uploaded/files/4328/fortios-v6.0.0-release-notes.pdf

Beta and interims have been good.

Nice Easter surprise.

[Kenundrum]

I'm reading through some of the documentation. I was interested in the fabric changes.

So far- you still cannot have VDOMs enabled and participate in a security fabric which is still ridiculous. Also- the guide appears to be inconsistent for setting up a fabric as far as what is required. The diagrams show that a fortianalyzer is required, but all the text makes it seem like it is optional by referring to it as a recommended item. As I understand it, in 5.4 you only needed fortigates, in 5.6 you need an analyzer to use fabric features. Is that requirement now dropped again? Unfortunately almost all my devices have multiple VDOMs (mixing transparent and NAT modes) so I haven't been able to verify myself.

[khj]

Totally agree.

I was excited about the new feature that attempts to make the swithcontroller work with mulitble VDOMs. I have not tried it yet, as the documentation says that some of the bare essentials like STP (and related), QoS, 802.1X etc. are not supported with this feature enabled.

It would be really helpful to know what is on the roadmap for VDOMs in the near future that actually works.

[ede_pfau]

@neonbit: FOS v5.4.8 fixes the 'policies all-expanded' GUI bug already.

[rkhair]

did the upgrade on my 100d, after i tested it on my DC 100d which was fine.. however the one in my office did the upgrade, comes up and all seems okay but cannot access the web interface through http or https.. ssh works fine and the firewall is letting traffic through and VPNs etc. are up, but the web interface on http or https is totally knackered! tried changing ports via SSH and enabling the http/https access on other interfaces, same thing!

Just a warning

[neonbit]

Upgraded 201E from 5.6.3 to 6.0 and working great for me so far. Tested local logging, SSLVPNs with RDP bookmarks and tunnel mode, VLANs,  dialupVPNs, DHCP sever and DNS server and all working fine so far.

Registered the FortiClient Linux (beta) to the FGT and it now shows up on the FGT (including my avatar).

I like how when you open the policy section it now defaults to the collapse all view instead of the expand all one like it was before.

One thing that I noted in the release notes is if you're upgrading from 5.6.3 > 6.0.0 you can't have any VLANs tied to an interface, and then have a zone referencing the interface and the zone. Hope it doesn't burn anyone that didn't read the notes!

All up very happy with this build so far, especially for a X.0 GA build.

[simonorch]

rkhair wrote:

did the upgrade on my 100d, after i tested it on my DC 100d which was fine.. however the one in my office did the upgrade, comes up and all seems okay but cannot access the web interface through http or https.. ssh works fine and the firewall is letting traffic through and VPNs etc. are up, but the web interface on http or https is totally knackered! tried changing ports via SSH and enabling the http/https access on other interfaces, same thing!

Just a warning

Just a thought, that sounds like a certificate issue (if you have redirect to https enabled as well)

Check the 'admin-server-cert' setting under conf sys global.

Simon

[rkhair]

Simon, you are a legend. Thx for pointing me in right direction. Not sure why it broke but I did this.. 1) Changed admin SSL port back to 443 2) the 'admin-server-cert' was showing '' so I assigned the factory one to it.. using... set admin-server-cert "Fortinet_Factory" Not sure why it lost it on upgrade. Hopefully helps someone else who loses web admin access after v6.0 upgrade.

simonorch wrote:

rkhair wrote:
did the upgrade on my 100d, after i tested it on my DC 100d which was fine.. however the one in my office did the upgrade, comes up and all seems okay but cannot access the web interface through http or https.. ssh works fine and the firewall is letting traffic through and VPNs etc. are up, but the web interface on http or https is totally knackered! tried changing ports via SSH and enabling the http/https access on other interfaces, same thing!   Just a warning

Just a thought, that sounds like a certificate issue (if you have redirect to https enabled as well) Check the 'admin-server-cert' setting under conf sys global.   Simon  

[emnoc]

Will  I bit the bullet , my new  FWF50E  has a fresh  v6.0 installed ;) The upgrade from v5.6.3 went off with zero issues. It did take a few longer minutes for the WebGUI to be present. I will upgrade a FWF60D next and see what a D model does.

FWF50E3U17002431 # get system status  |  grep ersion Version: FortiWiFi-50E v6.0.0,build0076,180329 (GA) BIOS version: 05000013 Release Version Information: GA

Ken