Resolved issues
The following issues have been fixed in FortiSwitchOS 7.2.3. For inquiries about a particular bug, please contact Customer Service & Support.
Bug ID | Description |
---|---|
806907 | Packet loss occurs when using the SP-CABLE-FS-SFP+5 direct-attach cable with FS-124F switches. |
818628 | When Virtual Router Redundancy Protocol (VRRP) is being used in a layer-3 MCLAG topology, static routes disappear after the FortiSwitch unit is restarted. |
833450 | Layer-2 multicast traffic is flooding to ports within the same VLAN, even though IGMP snooping is enabled. |
833503 |
The FortiGate device does not detect a standalone FS-224E-POE that is running FortiSwitchOS 7.0.5. |
834930 | The diagnose switch mclag peer-consistency-check command displays split ports incorrectly. |
837168 |
The following switches make a high fan noise:
|
838908, 861167 |
The event log erroneously reports “FAN failure detected” on multiple FS-248E-POE switches. |
844973 | After the firmware is successfully uploaded, the FS-M426E switch fails to upgrade. |
845190 | FortiSwitchOS will not allow https to be removed from the set allowaccess configuration. |
846994 | Configuring the set group-name under config match for config user tacacs+ does not work. |
849465 |
Using FN-TRAN-GC with the FS-108E or FS-108F switch causes link flapping or wrongly shows that the link is up when the cable is not connected. |
850859 |
FortiSwitchOS sends the wrong OID for the SNMPv3 trap for link-down events. |
857391 |
After upgrading FortiSwitchOS, multiple FS-448E switches report that the fan has failed, although the fan status is OK. |
861492 | The mgmt interface MAC address is set to 00:01:02:03:04:05 after a reboot or factory reset. |
863009 |
When running FortiSwitchOS 7.2.2, the RPS LED does not light with the appropriate color when a redundant power supply is inserted. |
866231 |
The |
Common vulnerabilities and exposures
Visit https://fortiguard.com/psirt for more information.
Bug ID | CVE references |
---|---|
855445 |
FortiSwitchOS 7.2.3 is no longer vulnerable to the following CVE Reference:
|