Local in and local out management sessions (for example, a continuous ping from a management PC to a FortiGate-6000 or 7000 management interface) received by a data interface, now correctly fail over to a different FPC or FPM when the FPC or FPM originally processing the session fails.

Resolved multiple issues that caused the slbrpcd process to crash.

Resolved an issue that caused a delay when the diagnose sys session full-stat command displays FortiGate-6000 management board statistics.

Resolved an issue that prevented starting packet capture after deleting and then re-creating the same packet capture configuration.

Resolved an issue that could prevent the secondary FortiGate-6000 or 7000 in an FGCP cluster from updating its license status after a license renewal.

Management traffic received by FortiGate-7000 data interfaces is now correctly routed to the FIM in slot 2 if the FIM in slot 2 is the primary FIM.

Resolved an issue that could cause processes such as hasync and hatalk to crash after an FGCP HA failover.

Resolved an issue that could prevent an FGCP cluster from synchronizing.

Resolved an issue that could prevent an interface in a LAG from sending LACPDUs to the switch that the interface is connected to.

Resolved an issue that caused the slbrpcd process to use 90% CPU on some FortiGate-6000 management board CPU cores.

Resolved an issue that blocked SYN/ACK packets from passing through a transparent mode VDOM if the packets were not processed by the primary FPC or FPM.

Resolved an issue that could cause unexpected interruptions, such as interface flapping, during a FortiGuard update.

Resolved an multiple issues with the ffdb process that could cause the confsyncd process to crash.

Resolved an issue that could prevent the secondary FortiGate-6000 or 7000 in an FGCP cluster from sending event logs to a syslog server.

Resolved an issue that could cause the fgfmsd process to crash when making configuration changes.

Resolved an issue that could sometimes prevent SNMP polling of FIM data from working as expected.

Resolved an issue that slowed GUI performance after an FGCP HA failover.

Resolved multiple issues that could cause the cmdbsvr process to crash. Resolved an issue that resulted in a cmdbsvr process crash causing HA heartbeat failure and blocking data traffic.

The miglogd process no longer uses up to 99% of CPU resources after a configuration change on systems with configurations that include a large number of firewall policies (for example, more than 10,000 policies).

Resolved an issue that would prevent an Antivirus log message from being produced when the URL pointing to a file being downloaded is very long. The long URL would be included in the log message and would result in a log message that was too long for the logging system to handle correctly.

Resolved an issue that could cause all FPMs to remain in waiting for management heartbeat status after the cluster renegotiated because of a configuration change or after a FortiGate-7000 rejoined the cluster.

Resolved an issue that caused the diagnose np np6 port-list command output to show the incorrect Max Speed for port26, port27, and port28.

Log messages generated by the secondary FortiGate-6000 or 7000 in an FGCP HA cluster are now sent directly to FortiAnalyzer or a syslog server instead of being relayed to the management board or primary FIM.

Resolved an issue that caused the hasync process to crash when a large number of users (around 100,000) log off over a short time interval.

Resolved an issue that caused connection problems with FSSO servers because of fragmented packets.

Resolved an issue with the HA graceful upgrade process that could temporarily block traffic during the upgrade.

Resolved an issue that sometimes prevented the FortiGate-7000 SMM from sending the correct chassis SN and other information to FortiOS.

Resolved an issue with how firewall address groups were stored that caused out-of-sync errors.

Resolved an issue that could cause the fcnacd process to crash after deleting a VDOM.

Resolved an issue that could cause entering the diagnose sys cmdb-profile command to crash the confsynccmdd process on all FPCs.

Resolved an issue that could cause one of the FortiGate-6000s or 7000s in an FGCP cluster to display the FortiCare support contract for the other FortiGate-6000 or 7000 in the cluster.

Resolved an issue that cause the message Unknown field name for "vfid" and "pid" to be displayed on the CLI console.