FAZ 5.6.1 is out.

[RobertReynolds]

https://docs.fortinet.com...r-v5.6.1-release-notes

[Hosemacht · Accepted solution]

Hi tanr,

we got fortios 5.4.7, 5.2.13 and fortimail 5.4.3

no issues so far, exept the syslog thing but this was introduced with 5.6.0

and maybe get patched with 5.6.2 like the support told me.

Regards

[chall_FTNT · Accepted solution]

If your FAZ VM is on ESXi, you need to remap the interfaces for that VM.  This change occurs when upgrading to FAZ 5.6.x from FAZ 5.4.x (or earlier).  For more details, see the release notes.

[gdoornenbal · Accepted solution]

Yes, that is the problem indeed.  But before the upgrade the port mappings were correct (Port1 -> Interface 1). After the upgrade it is now Port1 ->Interface 4.

So i'm not too happy about that.

[fred]

Just did an upgrade, and when the system came up most of my devices were red/down. Ping from both sides were ok. Testing the connection under log settings did not help. I figured I would give the FortiAnalyzer a reboot, and after that all was back to normal.. just as a tip for anyone wanting to upgrade..

[jyang_FTNT]

Hi Fred,

When you see the upgrade issue, could you please let me know the upgrade path? Thanks.

[Ray · Accepted solution]

We ran into the same network problem as gdoornenbal.

We used to have port1 mapping to "Network Adapter1" on 5.4.4. We lost the network connection after upgrade to 5.6.1.

We had to go to VMware to disable "Network Adapter1" and enable ""Network Adapter4"

This is the opposite of the description on page 10 of https://docs.fortinet.com...r-v5.6.1-release-notes

[Baptiste]

Ray wrote:

We ran into the same network problem as gdoornenbal.

We used to have port1 mapping to "Network Adapter1" on 5.4.4. We lost the network connection after upgrade to 5.6.1.

We had to go to VMware to disable "Network Adapter1" and enable ""Network Adapter4"

This is the opposite of the description on page 10 of https://docs.fortinet.com...r-v5.6.1-release-notes

Thanks, same issue for me too (upgrade from 5.4.3).