ADC Release 3.1 Instrukcja Użytkownika Strona 6

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 13
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 5
Fortinet Technologies Inc. 6 FortiADC 4.0 Patch Release 5 E Series Release Notes
Resolved Issues
This release addresses a major security vulnerability. See Bug ID 9011 on the following
page. All customers should upgrade to this release as soon as possible.
This section lists the major issues that have been fixed since the last release. For inquires about
a particular bug, please contact Customer Support.
Table 1: Resolved Issues.
Bug ID
Description
8609
8886
Troubleshooting: Added additional SSL / HTTPS debugging information to
save state archives to aid in problem analysis.
8857
Failover: In certain cases where both systems are attempting to assume
primary mode, traffic is sent to the backup system instead of the system that
actually became primary. Failover has been modified so that whenever a
system assumes primary mode, it will always send out Gratuitous ARPs for all
the IP addresses it owns. (1097050)
8859
Restore: Restoring a backup archive taken on one model to another model
results in limited or no network availability after the restore is complete. This
bug has been fixed
8875
Restore and Failover: Failover does not always re-configure itself properly in
this scenario:
1. Assume two units (A, B) are in failover.
2. Unit A is taken offline.
3. A new unit (C) is brought online to replace unit A, and a backup archive
from unit A is restored onto unit C.
4. Unit C is then powered off, and unit A is brought back online.
After the last step above, failover between the units A and B is not established
properly. This bug has been fixed. (1082880)
[Note that if unit A was only disconnected from the network and not shut down
during Step 2 above, a reboot of unit A in Step 4 will be required in order to
synchronize failover between the two units properly.]
8882
Active-Active Failover: Fixed issues that could prevent one or more units from
entering failover when several peers are added quickly to the configuration.
8890
Troubleshooting: Taking a save state archive on some systems can impact
the systems ability to process incoming connections during periods of high
traffic. This bug has been fixed. (1156042)
8896
Failover: Fixed an issue that could cause all peers to go into backup mode if
the failover IP address was also being used in a subnet NAT (Network Address
Translation) rule. (1097050)
Przeglądanie stron 5
1 2 3 4 5 6 7 8 9 10 11 12 13

Komentarze do niniejszej Instrukcji

Brak uwag