Fortigate Firewall - Reduced Network Capacity

This incident has been resolved.

This failover is now complete.

Please update or raise a case in the MySAU portal if you are experiencing any further issues.

We are currently in the process of promoting the SY3 Firewall HA member back to primary after changes made by our Network Operations Team and the vendor earlier this morning.

No customer impact is expected.

Per recommendation from the vendor, we will leave the HA cluster un the current state and monitor the situation further. Services should be operating as normal, and no further switchovers are required. The vendor has confirmed that the issue is resolved in a firmware release that is scheduled for late April. Engineers will monitor the status of the cluster until the firmware update is available, and pre-emptively perform a switchover should the cluster approach the memory consumption threshold recommended by the vendor.

If you have any questions or continue to experience issues, please raise a case via the MySAU portal.

Firewall switchover has occurred, and the former standby unit is now the primary. Engineers will perform some further diagnostics and then reboot the standby unit to clear the error condition.

Further updates will be provided as available.

To implement the workaround on the Primary Device, we need to failover workloads to the redundant side of this Firewall Cluster.

This process should not impact workloads further, but we are issuing a cautionary advisory that there may be a brief disruption when this happens.

Once the workaround is put in place, the cluster will be restored to full synchronous HA configuration

The vendor has identified a possible firmware issue.

The Fortinet team is currently working with us to implement a workaround while the root cause is investigated further.

We have had a number of customers advise that they are experiencing network capacity constraints when routing through our Sydney FortiGate Firewall Cluster.

We have identified that there is an issue with the device memory and that throughput is constrained.

Our Network Operations team has been engaged and they are working with FortiNet support to find the root cause of the issue.

Updates to Follow