Resolved issues
The following issues have been fixed in FortiOS 7.2.6. For inquiries about a particular bug, please contact Customer Service & Support.
| Bug ID | Description |
|---|---|
| 848632 | After upgrading to FortiOS 6.4.9 or 6.4.10, the link to the managed switch does not come up. |
| 858749 | Redirected traffic should not hit the firewall policy when allow-traffic-redirect is enabled. |
|
875382 |
When accessing the Managed FortiAP or Managed FortiSwitches view with a large number of devices in the topology, the page would take a long time to load. |
|
893405 |
After discovery, one transmit buffer was allocated and was not released when the connection was terminated. |
| 894735 | Users should be able to use the same EMS tags in multiple NAC policies on different FortiSwitch groups. |
| 902338 | If you configure multitenancy in the CLI and then add another VLAN in the GUI, the VLAN is removed from the other VDOM. |
|
904640 |
When a FortiSwitch port is reconfigured, the FortiGate device might incorrectly retain old detected device data from the port that results in an unexpected number of detected device MAC addresses for the port. Using |
| 911232 |
The security rating shows an incorrect warning for unregistered FortiSwitch units on the WiFi & Switch Controller > Managed FortiSwitches page. |
|
920231 |
When the FortiGate device is rebooted, the configuration for |
|
924654 |
The MAC address flaps on the FortiSwitch unit when a UDP packet passes through a virtual wire pair multiple times with ASIC offload. |
|
936081 |
When the FortiGate device is rebooted, the VLAN-optimization and vlan-all-mode settings disappear and cannot be restored in the CLI. |
|
941673 |
FortiSwitch events should be listed in the log with the configured FortiSwitch name, instead of the FortiSwitch serial number. |