Fortinet white logo
Fortinet white logo

Resolved issues

Resolved issues

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

Bug ID

Description

1213980 In a VRRP Active-Active cluster, cloning a global DNS policy with a large number of A/AAAA records caused the primary node’s Web GUI to hang and return “Bad Gateway” errors.
1212271 New CLI options are added to adjust the physical interface ring buffer size. Administrators can now configure rxring and txring values under config system interface and verify settings with the diagnose hardware get deviceinfo nic-ringsize command.
1205106 In the GUI, the Add Filter option under Network Security > Firewall was incorrectly grayed out and unavailable.
1200598 When HTTPS service was enabled on port2 and port3 in an Active-Active HA cluster, a node could drop out of the cluster due to a GLB process binding failure during HA synchronization. The issue caused temporary cluster instability until the node rejoined.
1194018 After upgrading to version 7.4.8, external connections could experience performance degradation due to dropped packets on the ingress ADC. The issue was caused by an incorrect check in the LRO/GRO handling logic that required TSO to be enabled, resulting in packet drops when receiving large packets assembled by LRO/GRO.
1192054 Maximum Request Header Value Length limit increased to 16,384.
1191529 Editing a virtual server in AP mode failed with a “traffic group conflict” error because traffic group validation was incorrectly applied outside HA VRRP mode.
1184789 FortiSandbox Cloud activation failed through a proxy with “FortiCloud internal error” due to an SSL read timing issue when responses were not received in time.
1184197 FortiADC licensed through FortiFlex remained restricted to VM01 limits despite valid VM08 entitlement due to incorrect CMDB tablesize handling after CPU allocation.

1049328

SNMP queries returned empty data for VLAN interfaces due to ethtool not reporting interface statistics.

Resolved issues

Resolved issues

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

Bug ID

Description

1213980 In a VRRP Active-Active cluster, cloning a global DNS policy with a large number of A/AAAA records caused the primary node’s Web GUI to hang and return “Bad Gateway” errors.
1212271 New CLI options are added to adjust the physical interface ring buffer size. Administrators can now configure rxring and txring values under config system interface and verify settings with the diagnose hardware get deviceinfo nic-ringsize command.
1205106 In the GUI, the Add Filter option under Network Security > Firewall was incorrectly grayed out and unavailable.
1200598 When HTTPS service was enabled on port2 and port3 in an Active-Active HA cluster, a node could drop out of the cluster due to a GLB process binding failure during HA synchronization. The issue caused temporary cluster instability until the node rejoined.
1194018 After upgrading to version 7.4.8, external connections could experience performance degradation due to dropped packets on the ingress ADC. The issue was caused by an incorrect check in the LRO/GRO handling logic that required TSO to be enabled, resulting in packet drops when receiving large packets assembled by LRO/GRO.
1192054 Maximum Request Header Value Length limit increased to 16,384.
1191529 Editing a virtual server in AP mode failed with a “traffic group conflict” error because traffic group validation was incorrectly applied outside HA VRRP mode.
1184789 FortiSandbox Cloud activation failed through a proxy with “FortiCloud internal error” due to an SSL read timing issue when responses were not received in time.
1184197 FortiADC licensed through FortiFlex remained restricted to VM01 limits despite valid VM08 entitlement due to incorrect CMDB tablesize handling after CPU allocation.

1049328

SNMP queries returned empty data for VLAN interfaces due to ethtool not reporting interface statistics.