Resolved issues
The following issues have been fixed in FortiGate-6000 and 7000 FortiOS 6.0.12 Build 0386. For inquires about a particular bug, please contact Customer Service & Support. The Resolved Issues described in the FortiOS 6.0.12 release notes also apply to FortiGate-6000 and 7000 FortiOS 6.0.12 Build 0386.
Bug ID |
Description |
---|---|
564049 |
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. |
579371 695419 |
Resolved multiple issues that caused the |
579375 |
Resolved an issue that caused a delay when the |
587437 |
Resolved an issue that prevented starting packet capture after deleting and then re-creating the same packet capture configuration. |
590997 |
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. |
596013 |
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. |
630070 |
Resolved an issue that could cause processes such as |
631342 |
Resolved an issue that could prevent an FGCP cluster from synchronizing. |
653636 |
Resolved an issue that could prevent an interface in a LAG from sending LACPDUs to the switch that the interface is connected to. |
653727 |
Resolved an issue that caused the |
657929 |
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. |
663706 |
Resolved an issue that could cause unexpected interruptions, such as interface flapping, during a FortiGuard update. |
666583 692943 |
Resolved an multiple issues with the |
669211 |
Resolved an issue that could prevent the secondary FortiGate-6000 or 7000 in an FGCP cluster from sending event logs to a syslog server. |
689042 |
Resolved an issue that could cause the |
689444 |
Resolved an issue that could sometimes prevent SNMP polling of FIM data from working as expected. |
690222 |
Resolved an issue that slowed GUI performance after an FGCP HA failover. |
691702 693013 |
Resolved multiple issues that could cause the |
693209 |
The |
693245 |
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. |
696711 |
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. |
696797 |
Resolved an issue that caused the |
698671 |
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. |
701302 |
Resolved an issue that caused the |
707572 |
Resolved an issue that caused connection problems with FSSO servers because of fragmented packets. |
708984 |
Resolved an issue with the HA graceful upgrade process that could temporarily block traffic during the upgrade. |
712835 |
Resolved an issue that sometimes prevented the FortiGate-7000 SMM from sending the correct chassis SN and other information to FortiOS. |
716933 |
Resolved an issue with how firewall address groups were stored that caused out-of-sync errors. |
717223 |
Resolved an issue that could cause the |
718344 |
Resolved an issue that could cause entering the |
718394 |
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. |
718823 |
Resolved an issue that cause the message |
719782 |
Resolved a synchronization issue that caused the management board of one of the FortiGate-6000s in an FGCP cluster to have the wrong MAC address in its MAC address database. |