Fortinet black logo

Resolved issues

Resolved issues

The following issues have been resolved in FortiADC 7.1.1 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID

Description

0850564 On the GCP platform, an address book conflict warning was falsely triggered due to memory overflow causing an expected error message in the /tmp/address_book_conflicts.log file.
0849916 SAML inserts a header persistent-id that contains 0x00 making HTTP requests invalid caused by the overflow of characters when the input value exceeds 1023.
0849784 Shell access crashed during upgrade to 7.1.1.
0848595 VDOM local admin is unable to create or modify reports.
0848099 The number of VDOMs that can be assigned to administrators through the GUI does not match the CLI. Through the GUI, only 10 VDOMs can be assigned to administrator, whereas 10+ VDOMs can be assigned through the CLI.
0847369 VDOM traffic-log does not work when VDOM capacity is exceeded. For VMs (16 or 32 CPU) the VDOM capacity should be 15 or 20, however the VDOM traffic-log stops working after 10 VDOMs are added. For hardware platforms, when the number of VDOMs exceed the capacity (32 in some platforms), the traffic-log does not work for the excess VDOM.
0847200 System Metrics traps using undocumented OID with meaningless information.
0846804 When configuring SNMP Community for Traps, the GUI does not prevent long strings from being saved. However, these long strings will be truncated when they exceed 64 characters when the SNMP Community is sent.
0846715/0840354 The VM can create up to 15 VDOMs after importing the 16 Cores license, but only 10 corresponding VDOM names are created in /var/log/logrpt/{VDOM}, where the logging for some of the VDOMs are not working.
0846513

Redirecting to HTTPS does not work due to HTTPS service not being enabled automatically on the management port.

0846337 When two virtual servers with the same IP address but different ports configured and one is disabled, the BGP stops advertising the IP for both virtual servers.
0846292

WAD failed to monitor files that contain special characters in the name.

0845726

Content routing match condition term "reverse" is ambiguous and does not clearly explain the condition.

0844072 Management IP unavailable after switching AP mode to standalone.
0840608 WAF Source IP exceptions stopped working for URL protection.
0840171 Route Health Injection leaking between VDOMs.
0839662 Ping fails when VLAN is created with special characters.

0839661

Improper grammar in error message.
0839521 In GCP, the licd fails to bind due to an improper bindkey type in the dhcpd that assigns a wrong bindkey to the cmdb.
0838537 Administrator who has read/write permission cannot upload certificate in VDOMs
0837825 Improper grammar in log messages.
0836867 Unexpected RHI behavior for in A-A-VRRP HA cluster.

0835909

In WAD, cannot delete the files on the server when the file names contain special characters.

0835425

RADIUS virtual server intermittently adds incorrect translated destination port in the forwarded RADIUS requests.

0832367

For Automation email actions, the number of times the action is triggered does not match the number of times the email alert is actually sent.

0829597

HA A-A mode secondary unit traffic log shows gateway as none.

0828919

L2 SSL Forward Proxy bypassed session and log show incorrect port information.

0827748

FortiADC devices showing consistent slowness.

0826635

FortiADC crashed after changing the virtual server type from Layer 4 to Layer 2.

0824287

Enhancement request to add SAN field for manual CSR creation in GUI and CLI.

0821812

Clock synchronization failure with local NTP server when the virtual server uses port 123, causing the NTP bind to fail.

0821776

Kernel panic while removing VLAN interface.

0820934

FortiADC GUI interfaces displaying as disabled.

0799996

There is no validation check when the certificate name exceeds the maximum character length.

0717843

HTML form authentication does not notify users when the authentication has failed.

Resolved issues

The following issues have been resolved in FortiADC 7.1.1 release. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID

Description

0850564 On the GCP platform, an address book conflict warning was falsely triggered due to memory overflow causing an expected error message in the /tmp/address_book_conflicts.log file.
0849916 SAML inserts a header persistent-id that contains 0x00 making HTTP requests invalid caused by the overflow of characters when the input value exceeds 1023.
0849784 Shell access crashed during upgrade to 7.1.1.
0848595 VDOM local admin is unable to create or modify reports.
0848099 The number of VDOMs that can be assigned to administrators through the GUI does not match the CLI. Through the GUI, only 10 VDOMs can be assigned to administrator, whereas 10+ VDOMs can be assigned through the CLI.
0847369 VDOM traffic-log does not work when VDOM capacity is exceeded. For VMs (16 or 32 CPU) the VDOM capacity should be 15 or 20, however the VDOM traffic-log stops working after 10 VDOMs are added. For hardware platforms, when the number of VDOMs exceed the capacity (32 in some platforms), the traffic-log does not work for the excess VDOM.
0847200 System Metrics traps using undocumented OID with meaningless information.
0846804 When configuring SNMP Community for Traps, the GUI does not prevent long strings from being saved. However, these long strings will be truncated when they exceed 64 characters when the SNMP Community is sent.
0846715/0840354 The VM can create up to 15 VDOMs after importing the 16 Cores license, but only 10 corresponding VDOM names are created in /var/log/logrpt/{VDOM}, where the logging for some of the VDOMs are not working.
0846513

Redirecting to HTTPS does not work due to HTTPS service not being enabled automatically on the management port.

0846337 When two virtual servers with the same IP address but different ports configured and one is disabled, the BGP stops advertising the IP for both virtual servers.
0846292

WAD failed to monitor files that contain special characters in the name.

0845726

Content routing match condition term "reverse" is ambiguous and does not clearly explain the condition.

0844072 Management IP unavailable after switching AP mode to standalone.
0840608 WAF Source IP exceptions stopped working for URL protection.
0840171 Route Health Injection leaking between VDOMs.
0839662 Ping fails when VLAN is created with special characters.

0839661

Improper grammar in error message.
0839521 In GCP, the licd fails to bind due to an improper bindkey type in the dhcpd that assigns a wrong bindkey to the cmdb.
0838537 Administrator who has read/write permission cannot upload certificate in VDOMs
0837825 Improper grammar in log messages.
0836867 Unexpected RHI behavior for in A-A-VRRP HA cluster.

0835909

In WAD, cannot delete the files on the server when the file names contain special characters.

0835425

RADIUS virtual server intermittently adds incorrect translated destination port in the forwarded RADIUS requests.

0832367

For Automation email actions, the number of times the action is triggered does not match the number of times the email alert is actually sent.

0829597

HA A-A mode secondary unit traffic log shows gateway as none.

0828919

L2 SSL Forward Proxy bypassed session and log show incorrect port information.

0827748

FortiADC devices showing consistent slowness.

0826635

FortiADC crashed after changing the virtual server type from Layer 4 to Layer 2.

0824287

Enhancement request to add SAN field for manual CSR creation in GUI and CLI.

0821812

Clock synchronization failure with local NTP server when the virtual server uses port 123, causing the NTP bind to fail.

0821776

Kernel panic while removing VLAN interface.

0820934

FortiADC GUI interfaces displaying as disabled.

0799996

There is no validation check when the certificate name exceeds the maximum character length.

0717843

HTML form authentication does not notify users when the authentication has failed.