Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

Known issues

This section lists known issues in FortiADC 7.0.3, but may not be a complete list. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID

Description

0833592 FortiADC fails to send files to FortiSandBox Cloud.
0829597 HA A-A mode secondary unit traffic log shows gateway as none.
0826540

In the GUI, failed to append child list when configuring Automation. This results when an alert type has reached the maximum entry capacity.

The current maximum is 256 entries for each alert type, as categorized in the backend CLI:

  • config system alert-policy

  • config system alert-action

  • config system alert

  • config system alert-email

  • config system alert-snmp-trap

  • config system alert-script

  • config system alert-webhook

  • config system alert-fortigate-ip-ban

  • config system alert-syslog

config system alert-policy configurations are often composed of multiple config system alert entries, making the config system alert most likely to exceed the entry capacity. Please use show full-configuration system alert for details in the CLI.

Workaround:

After figuring out which alert type has exceeded the 256 entry capacity from the backend CLI, remove any unused automation alerts from the GUI.

0816798

In an HA environment, if you are using a predefined automation configuration, resetting the configuration through the GUI (using the reset button) or unsetting comments through CLI will cause the HA synchronization to fail whenever a device reboots and rejoins the cluster.

Using the GUI reset button resets the predefined configuration values to the predefined default values, all except the comments value which is set to the default value on the backend. For example, if using the HA predefined configuration, the reset will result in set comments HAset comments comments. When a new device (or a rebooted device) joins the HA cluster, the synchronization will fail due to the mismatched set comments value between the device that has the predefined default value (set comments HA) and the reset device that has the default value (set comments comments).

In the CLI, if set comments in the predefined configuration has been unset and is the default value set comments comments, then the same HA synchronization issue will occur.

Workaround:

In the CLI, edit set comments to ensure it is not the default value (set comments comments) and it matches the value of the predefined configuration (for example, set comments HA).

Known issues

This section lists known issues in FortiADC 7.0.3, but may not be a complete list. For inquiries about particular bugs, please contact Fortinet Customer Service & Support.

Bug ID

Description

0833592 FortiADC fails to send files to FortiSandBox Cloud.
0829597 HA A-A mode secondary unit traffic log shows gateway as none.
0826540

In the GUI, failed to append child list when configuring Automation. This results when an alert type has reached the maximum entry capacity.

The current maximum is 256 entries for each alert type, as categorized in the backend CLI:

  • config system alert-policy

  • config system alert-action

  • config system alert

  • config system alert-email

  • config system alert-snmp-trap

  • config system alert-script

  • config system alert-webhook

  • config system alert-fortigate-ip-ban

  • config system alert-syslog

config system alert-policy configurations are often composed of multiple config system alert entries, making the config system alert most likely to exceed the entry capacity. Please use show full-configuration system alert for details in the CLI.

Workaround:

After figuring out which alert type has exceeded the 256 entry capacity from the backend CLI, remove any unused automation alerts from the GUI.

0816798

In an HA environment, if you are using a predefined automation configuration, resetting the configuration through the GUI (using the reset button) or unsetting comments through CLI will cause the HA synchronization to fail whenever a device reboots and rejoins the cluster.

Using the GUI reset button resets the predefined configuration values to the predefined default values, all except the comments value which is set to the default value on the backend. For example, if using the HA predefined configuration, the reset will result in set comments HAset comments comments. When a new device (or a rebooted device) joins the HA cluster, the synchronization will fail due to the mismatched set comments value between the device that has the predefined default value (set comments HA) and the reset device that has the default value (set comments comments).

In the CLI, if set comments in the predefined configuration has been unset and is the default value set comments comments, then the same HA synchronization issue will occur.

Workaround:

In the CLI, edit set comments to ensure it is not the default value (set comments comments) and it matches the value of the predefined configuration (for example, set comments HA).