Fortinet black logo

Resolved issues

Resolved issues

The following issues have been fixed in FortiOS 7.4.0. For inquiries about a particular bug, please contact Customer Service & Support.

Bug ID Description

730472

Initial ARP resolutions are slow when FortiSwitch-enabled VLANs are using access VLANs and proxy ARP.

762615, 765283

The FortiLink flcfg daemon crashes when the configurations pushed to the FortiSwitch unit include the quarantine MAC addresses.

828901

FortiSwitch and FortiAP units are disconnected when the wireless system daemon (hostapd) crashes.

848822

The Security Rating page incorrectly lists the version number of the 7.2 FortiAP and FortiSwitch firmware as unknown.

853414

After upgrading from 7.0.5 to 7.0.7, the Policy and Dashboard widgets do not load when the FortiGate device manages a FortiSwitch unit with tenant ports.

853811

The Link Aggregation Control Protocol (LACP) flaps after the interfaces connecting to LACP are shut down and then restarted from the switch side.

857778

When a VLAN is changed on a FortiGate device, the changes are pushed to the managed FortiSwitch unit but do not take effect.

858113

When the admin profile was created on a FortiGate device, the Diagnostics and Tools page for a FortiSwitch unit cannot be displayed with limited access permissions.

858749

Redirected traffic should not hit the firewall policy when allow-traffic-redirect is enabled.

859845

Sometimes the correct host names for access points are not displayed in the FortiSwitch Ports window.

870083 The FortiGate HA cluster is unsynchronized because of mismatched configurations on the FortiLink interface.
876021 After the FortiGate device is restarted, the FortiLink virtual managed-switch port status is not pushed.

886887

The FortiAnalyzer event log receives too many messages about FortiSwitch MAC entries being discovered.

892576

Previously, the set rate command (under config switch-controller storm-control and config switch-controller managed-switch) could not be set to 0.

894735

Users should be able to use the same EMS tags in multiple NAC policies on different FortiSwitch groups.

Resolved issues

The following issues have been fixed in FortiOS 7.4.0. For inquiries about a particular bug, please contact Customer Service & Support.

Bug ID Description

730472

Initial ARP resolutions are slow when FortiSwitch-enabled VLANs are using access VLANs and proxy ARP.

762615, 765283

The FortiLink flcfg daemon crashes when the configurations pushed to the FortiSwitch unit include the quarantine MAC addresses.

828901

FortiSwitch and FortiAP units are disconnected when the wireless system daemon (hostapd) crashes.

848822

The Security Rating page incorrectly lists the version number of the 7.2 FortiAP and FortiSwitch firmware as unknown.

853414

After upgrading from 7.0.5 to 7.0.7, the Policy and Dashboard widgets do not load when the FortiGate device manages a FortiSwitch unit with tenant ports.

853811

The Link Aggregation Control Protocol (LACP) flaps after the interfaces connecting to LACP are shut down and then restarted from the switch side.

857778

When a VLAN is changed on a FortiGate device, the changes are pushed to the managed FortiSwitch unit but do not take effect.

858113

When the admin profile was created on a FortiGate device, the Diagnostics and Tools page for a FortiSwitch unit cannot be displayed with limited access permissions.

858749

Redirected traffic should not hit the firewall policy when allow-traffic-redirect is enabled.

859845

Sometimes the correct host names for access points are not displayed in the FortiSwitch Ports window.

870083 The FortiGate HA cluster is unsynchronized because of mismatched configurations on the FortiLink interface.
876021 After the FortiGate device is restarted, the FortiLink virtual managed-switch port status is not pushed.

886887

The FortiAnalyzer event log receives too many messages about FortiSwitch MAC entries being discovered.

892576

Previously, the set rate command (under config switch-controller storm-control and config switch-controller managed-switch) could not be set to 0.

894735

Users should be able to use the same EMS tags in multiple NAC policies on different FortiSwitch groups.