Resolved issues
This section highlights the major known issues discovered in FortiADC 5.3.1 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.
Known issues
| Bug ID | Description |
|---|---|
| 0566984 | Need comment/notes for Admin IDs |
| 0568261 | KVM image failed to deploy on Apache CloudStack |
| 0569029 | Execute formatlogdisk failed on XenOpen/XenServer |
| 0568535 | Changed GSLB CNAME target name limit from 48 to 255 |
| 0556245 | Threat Map does not show anything in some cases |
| 0564257 | Fortiview session filter resets after refresh |
| 0565387 | WAF "web scraping" may have different name in log |
| 0563858 | Optimize 4000F boot up time |
| 0570321 | ADC VM on AWS drops 5% packets for the ping ICMP packets |
| 0563296 | LDAP Fetch data format is different from 4.8.x |
| 0554087 | GLB vulnerability CVE-2018-5743 fix |
| 0525665 | FortiADC uses DH public key size to 127 bytes in DHE_RSA Client Key Exchange message during Healthcheck caused failures. |
| 0568810 | Log message "DROPPED DUE TO CONN_SCHED_UNREACH" |
| 0557573 | FortiADC OCI SDN connector needs to cover all OCI regions |
| 0571274 | Default MTU is 1450 for KVM On Nutanix, changed it back to 1500 |
| 0568369 | Used incorrect certificate to server side for https health-check |
| 0571886 | Unexpected reboot happened, may cause coredump and link down |
| 0535558 | Add HA and allow access information on Network Interface ports |