Known issues
The following issues have been identified in FortiGate-6000 and FortiGate-7000 FortiOS 6.0.9 Build 6783. For inquires about a particular bug, please contact Customer Service & Support. The Known Issues described in the FortiOS 6.0.9 release notes also apply to FortiGate-6000 and 7000 FortiOS 6.0.9 Build 6783.
Bug ID |
Description |
---|---|
508610 |
FortiGate-6000 and 7000 interface status LEDs do not accurately show link status for copper SPF transceivers that use the RX_LOS pin to indicate link status. |
600879 | The feature to enable packet capturing from a firewall policy is not available. |
611558 |
In some cases on a FortiGate-7000, configuration changes may not successfully be synchronized to all of the FPMs. If this occurs you can run the command |
612622 | Quarantined files are not sent to FortiSandbox when the config system fortisandbox configuration includes a setting for the source-ip option. |
616110 |
After an FGCP HA failover, its possible that traffic may not be able to pass through a transparent mode VDOM until the FDB MAC table expires in approximately 6 minutes. |
616728 |
If you factory reset the backup FortiGate-6000 or 7000 in an FGCP cluster and then re-configure the backup FortiGate to join with the correct HA settings, the backup FortiGate will not be able to join the cluster again until it is manually restarted. |
619094 |
In an FGSP configuration with asymmetric routing and four FortiGate-6000s or 7000s, the first reply packet of all new sessions is dropped. |
619237 |
When a FortiGate-6000 or 7000 is idle, the |
621375 |
A graceful upgrade of an FGCP HA cluster may fail if the configuration includes a large number of VDOMs. The upgrade process times out waiting for the backup FortiGate-6000 or 7000 to upgrade and start up. |
621978 | VRRP packets that should be blocked are incorrectly sent to the secondary FPCs or FPMs. |