Fortinet black logo

Known issues

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

Bug ID

Description

0851364 VM return 20 instead of 10 for SNMP fadc vd max vdoms .1.3.6.1.4.1.12356.112.2.1.2
0850738 Occasionally, SSH cannot log admin into FortiADC.
0847993 The DNS related items are not hidden in report settings in non-root ADOM mode.
0836337 Virtual servers in non-root will not be synchronized to GLB if ADOM mode is enabled.

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).

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

Bug ID

Description

0851364 VM return 20 instead of 10 for SNMP fadc vd max vdoms .1.3.6.1.4.1.12356.112.2.1.2
0850738 Occasionally, SSH cannot log admin into FortiADC.
0847993 The DNS related items are not hidden in report settings in non-root ADOM mode.
0836337 Virtual servers in non-root will not be synchronized to GLB if ADOM mode is enabled.

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).