Known issues
The following issues have been identified in FortiGate-6000 and 7000 5.6.11 Build 4279. For inquires about a particular bug, please contact Customer Service & Support.
| Bug ID | Description |
|---|---|
| 459424 |
Statistics on the System > VDOM GUI page may be incorrect. |
|
474410 |
In-band management through traffic interfaces is not supported for FortiOS 5.6.11. |
|
537861 |
An FPM of a FortiGate-7000 in an HA cluster may become unresponsive and require a manual restart of the FPM to restore service. |
|
549983 |
FortiManager in-band management connections to the IP address of a VDOM link interface are not supported. |
|
561722 |
Firewall policies designed to identify traffic from known devices may not be able to detect traffic from the known devices. |
| 562773 |
In some cases and more often in an FGCP HA cluster, FortiGuard rating services may not be synchronized to all FPCs or FPMs. |
| 570796 |
Scheduled FortiGuard updates of a HA cluster may cause management heartbeat loss resulting in an HA failover. |
|
575568 |
Transparent mode HA may not respond as expected if a monitored interface goes down but then comes back up quickly. In this situation gratuitous ARP packets may fail to update the mac addresses on attached switches. |
|
575916 |
During a graceful upgrade of a FortiGate-6000 HA cluster, the backup FortiGate-6000 may become the primary before all of the FPCs in the new primary FortiGate-6000 are synchronized. |
|
578485 |
During a graceful upgrade of a FortiGate-7000 HA cluster, the backup FortiGate-7000 may become the primary before all of the FPMs in the new primary FortiGate-7000 are running the new firmware image. |
| 579284 |
A segmentation fault (signal 11) may cause version 3.543 of the IPS engine to crash. |
| 579836 |
Adding and removing multiple VLAN interfaces may cause error messages to appear on the CLI and can result in the CLI and GUI becoming unresponsive. A system restart may be required to access the system. |
| 583124 |
Incorrect usage information may be sent to a RADIUS server. Usage information can include the amount of data downloaded by a user or the amount of time that a user is connected. |
| 584078 |
Server load balancing real server status may not be synchronized to all FPCs or FPMs. |
| 584127 |
In some cases, changes to active firewall policies may not be synchronized to all FPCs or FPMs. |
|
584420 |
Because of synchronization issues between FPCs or FPMs, a captive portal configuration may block user access after the user has successfully authenticated. |
|
584800 |
The |
| 585239 |
Traffic logs may show unexpected results because outgoing short-lived UDP sessions may be directed to the wrong FPC or FPM. |