Fortinet Technologies Inc. 8 FortiADC 4.0 Patch Release 5 E Series Release Notes
Known Issues
This section lists the major known issues in this release, but is not a complete list. For inquires
about a particular bug, please contact Customer Support.
Table 2: Known Issues.
Match Rules: debug_message(), ssl2(), ssl3(), and tls1() functions (supported in
Version 8) are not accepted for expressions.
Clusters: The ‘Reset on server failure’ global option supported in previous releases is
not yet implemented in Version 10.
Layer 4 UDP clusters: The ‘persist override’ flag on UDP cluster server instances
does not override persistence.
TCP/ACV Health Checks: The CLI and Web UI will indicate that a server instance is
'ACV DOWN' (or not responding to ACV probes) even when ACV is not set, when the
server is not responding to TCP probes. It should be shown as ‘L4 TCP DOWN’. In any
case, the server is correctly marked ‘down’.
Health Checks: In a server pool configuration, do not define more than 16 health
check instances per server instance. If 17 health check instances are defined on a
server instance, the system will become unresponsive and reboot. The workaround,
after the system comes back up, is to remove the 17th health check from the
configuration file. This bug will be fixed in a future release.
VMware Integration: In a VMware configuration where Microsoft Active Directory is
used, logging in to VMware will fail if the VMware account used to log into VMware is
defined within an Active Directory domain. On VMware the login succeeds, but from
FortiADC the login attempt fails. If you test the login, it will appear to hang. Messages
like the following appear in the log: “vlbd[22043]: |e|v vCenter;|75000039: unable to
send message|Message too long|”.The workaround is to use a VMware account that is
not defined within Active Directory to log into VMware.
Modifying VLAN MTU: If you modify a VLAN MTU parameter to a value that is lower
than the currently set value, you must reboot to ensure proper operation of the network
interface.
Layer 4 UDP clusters: A server defined on the ADC cannot access any UDP clusters
defined on the ADC. This bug will be fixed in a future release.
Responders: It is not possible to enter a regular expression containing a "?" character
using the CLI. The workaround is to use the Web UI instead
SSH: When using SSH to log into the CLI, the file editor (for certificates, responders,
etc.) may not work. This may be due to the terminal type presented to the system on
login. To work around this issue, modify your terminal emulator settings before logging
in and set the terminal type to ‘xterm’.
Web UI: Cannot define an SNMP Trap server in the Web UI. The workaround is to use
the CLI.
(134 strony)
(2 strony)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji