FortiSwitchOS 7.4.7 Release Notes
FortiSwitchOS 7.4.7 Release Notes
FortiSwitchOS 7.4.7
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
NSE INSTITUTE
https://training.fortinet.com
FORTIGUARD CENTER
https://www.fortiguard.com
FEEDBACK
Email: [email protected]
Change log 4
What’s new in FortiSwitchOS 7.4.7 5
Introduction 6
Supported models 6
Special notices 7
SSH host keys must be regnerated and user certificates must be imported again when
downgrading from FortiSwitchOS 7.4.6 and later 7
Upgrading MCLAG peer group switches from FortiSwitchOS 7.4.2 and earlier to
FortiSwitchOS 7.4.3 and later 7
Reduce configuration revisions before downgrading from 7.4.2 and later versions 8
Zero-touch management 8
By default, auto-network is enabled in FortiSwitchOS 7.2.0 and later 8
Downgrading FortiSwitchOS 7.0.0 and later to versions earlier than 6.2.6 or 6.4.4 is not
supported 9
Downgrading your FortiSwitchOS version requires converting the admin password format
first 9
Connecting multiple FSR-112D-POE switches 10
Upgrade information 11
Product integration and support 12
FortiSwitchOS 7.4.7 support 12
Resolved issues 13
Known issues 15
Change log
Introduction
This document provides the following information for FortiSwitchOS 7.4.7 build 0914:
l Supported models on page 6
l Special notices on page 7
l Upgrade information on page 11
l Product integration and support on page 12
l Resolved issues on page 13
l Known issues on page 15
See the Fortinet Document Library for FortiSwitchOS documentation.
Supported models
Special notices
When FortiSwitchOS 7.4.6 or later is downgraded, users need to regenerate the SSH host keys and import the user
certificates again.
FortiSwitchOS 7.4.3 has changes in the MCLAG ICL communication that are incompatible with previous versions;
therefore, the upgrade of the MCLAG peer group will have a longer impact than usual. Below are the recommended
procedures.
The following recommended procedure will minimize downtime when upgrading MCLAG (the expected impact is within
20 seconds) from FortiSwitchOS 7.4.2 and earlier to FortiSwitchOS 7.4.3 and later.
1. If MCLAG split-brain protection is enabled, disable it in both switches in the MCLAG peer group.
2. In the FortiSwitchOS CLI, use the diagnose switch mclag icl command to find out which switch has the
lower MAC address. .
3032E-1 # diagnose switch mclag icl
_FlInK1_ICL0_
icl-ports 1-2
egress-block-ports 3-5,31.1,32.1,17.3,17.4,31.2,32.2,32.3,32.4
interface-mac 84:39:8f:13:96:4d <-- local switch MAC address
local-serial-number FS3E32T422000275
peer-mac 84:39:8f:13:99:59 <-- peer switch MAC address
peer-serial-number FS3E32T422000281
Local uptime 0 days 23h:55m: 0s
Peer uptime 0 days 23h:55m: 0s
MCLAG-STP-mac 84:39:8f:13:96:4c
keepalive interval 1
keepalive timeout 60
dormant candidate Peer
split-brain Disabled
3. Stage the image in both switches using the execute stage image CLI command)
4. Restart the switch with the lower MAC address.
In the preceding example, the local switch has the lower MAC address, so the local switch should be restarted first
5. Wait for the switch to restart and check that all links come up (the LACP trunks could be in a down state).
6. Restart the other switch.
7. After MCLAG comes up, enable split-brain protection if it was enabled before the upgrade.
For the FS-4xx, FS-5xx, FS-6xx, FS-1024E, FS-1048E, FS-3032E, FS-T1024E, and FS-2048F models only: If you
are downgrading from FortiSwitchOS 7.4.2 and later, you cannot have more than 20 saved configuration revisions.
Zero-touch management
When a new FortiSwitch unit is started, by default, it will connect to the available manager, which can be a FortiGate
device, FortiLAN Cloud, or FortiSwitch Manager. All ports are enabled for auto discovery. The “internal” interface is the
DHCP client in all FortiSwitch models. If you do not want your FortiSwitch unit to be managed, you must disable the
features that you do not want active.
After an execute factoryreset command is executed on a FortiSwitch unit in standalone mode, the auto-network
configuration is enabled by default. If you are not using auto-network, you must manually disable it:
config switch auto-network
set status disable
end
Downgrading FortiSwitchOS 7.0.0 and later to FortiSwitchOS 6.2.6 and later 6.2 versions is supported. Downgrading
FortiSwitchOS 7.0.0 and later to FortiSwitchOS 6.4.4 and later 6.4 versions is supported. Downgrading FortiSwitchOS
7.0.0 to versions earlier than FortiSwitchOS 6.2.6 or 6.4.4 is not supported.
Before downgrading to a FortiSwitchOS version earlier than 7.0.0, you need to ensure that the administrator password is
in SHA1 format. Use the execute system admin account-convert-sha1 command to convert the administrator
password to SHA1 encryption.
Before downgrading to FortiSwitchOS 7.0.0 or later, you need to ensure that the administrator password is in SHA1 or
SHA256 format.
l Use the execute system admin account-convert-sha1 command to convert the administrator password
to SHA1 encryption.
l Use the execute system admin account-convert-sha256 command to convert the password for a
system administrator account to SHA256 encryption.
If you do not convert the admin password before downgrading, the admin password will not
work after the switch reboots with the earlier FortiSwitchOS version.
1. Enter the following CLI command to convert the admin password to SHA1 encryption:
1. Enter the following CLI command to convert the admin password to SHA256 encryption:
The FSR-112D-POE switch does not support interconnectivity to other FSR-112D-POE switches using the PoE ports.
Fortinet recommends using the SFP ports to interconnect switches.
Upgrade information
If you do not follow the two-step upgrade process, the FortiSwitch unit will not start
after the upgrade, and you will need to use the serial console to conclude the upgrade
(BIOS and OS).
For FortiSwitch units managed by FortiGate units, refer to the FortiLink Release Notes for upgrade information.
The following table lists FortiSwitchOS 7.4.7 product integration and support information.
FortiOS (FortiLink Refer to the FortiLink Compatibility table to find which FortiSwitchOS versions support which
Support) FortiOS versions.
Resolved issues
The following issues have been fixed in FortiSwitchOS 7.4.7. For inquiries about a particular bug, please contact
Customer Service & Support.
Bug ID Description
1087244 After upgrading the switch to FortiSwitchOS 7.2.5, the FortiSwitch unit is unresponsive.
1091216 After a random power outage caused the FortiSwitch unit to restart, the switch configuration is lost.
1097393 The FSW-148F-FPOE model is not providing power to a third-party access point.
1098018 When performing 802.1x EAP authentication, authentication will fail if the RADIUS server sends
jumbo frames.
1099627 There is a delay in MAC address learning on the ICL trunk interface for the FS-6xxF models.
1101944 The FortiSwitch unit is not providing power to a specific VoIP phone (Grandstream GXP2160 model).
1108484 The PoE splitter does not work with the FS-148F-FPOE model.
1112481 STP topology change notifications and LACP trunk flapping occur during an SNMP walk on the FS-
624F-FPOE model.
1114261 The switch logs showed that the SFP module was removed from the switch ports 24, 25, 26, 27, and
28 and inserted back after 2 seconds.
1117174 The automation stitch should run without issues when %%date%% is used on the file name under the
automation action configuration.
1119673 In a FortiLink environment, the FortiSwitch VRRP configuration should not be deleted after a reboot.
1119678 The password for the RADIUS server is not being saved on FortiSwitch unit.
1120734 There is a delay in the display when the multicast stream is changed.
1122248 The remark-dscp action is not working in the egress ACL for the FS-6xxF models.
1124465 There is a high fan noise coming from the FS-124F-POE model.
1128640 The interswitch link (ISL) is not displayed in a FortiLink over a point-to-point layer-2 network.
1128657 Upgrading FortiSwitchOS from 7.0.6 to 7.4.6 or 7.6.1 causes the ICL trunk to change the native VLAN
to 4094 and the allowed VLANs to 1-4094.
1129639 When performing a traceroute to the FortiGate device from the PC in an MCLAG topology, the IP
addresses of the standalone switches are missing.
1129689 There is a “500 Internal Server Error” on the FS-6xxF models when the user tries to create an
ingress/egress ACL policy using the FortiSwitchOS GUI.
1131249 After restarting FS-4xxE switches, the PoE status and the state of the AP trunk member port on
MCLAG set to “disabled disabled.”
Bug ID Description
1136109 In the FS-624F model, the QoS queue should drop packets that exceed the limit instead of bringing
down CAPWAP tunnel.
1140195 After enabling DHCP snooping, there is high memory usage. This affects broadcast packets only; it
does not affect unicast packets.
1159503 For FortiSwitchOS 7.4.x and higher on the FSW-224E-POE model, ERSPAN randomly stops because
the MAC table is not being updated.
Known issues
The following known issues have been identified with FortiSwitchOS 7.4.7. For inquiries about a particular bug or to
report a bug, please contact Fortinet Customer Service & Support.
Bug ID Description
382518, 417024, DHCP snooping and dynamic ARP inspection (DAI) do not work with private VLANs
417073, 417099, (PVLANs).
438441
414972 IGMP snooping might not work correctly when used with 802.1x Dynamic VLAN functionality.
480605 When DHCP snooping is enabled on the FSR-112D-POE, the switched virtual interface (SVI)
cannot get the IP address from the DHCP server
Workarounds:
l Use a static IP address in the SVI when DHCP snooping is enabled on that VLAN.
l Temporarily disable DHCP snooping on the VLAN and then use the execute
interface dhcpclient-renew <interface> command to renew the IP address.
After the SVI gets the IP address from the DHCP server, you can enable DHCP
snooping.
510943 The time-domain reflectometer (TDR) function (cable diagnostics feature) reports unexpected
values.
Workaround: When using the cable diagnostics feature on a port (with the diagnose
switch physical-ports cable-diag <physical port name> CLI command),
ensure that the physical link on its neighbor port is down. You can disable the neighbor ports
or physically remove the cables.
542031 For the FS-5xx switches, the diagnose switch physical-ports led-flash
command flashes only the SFP port LEDs, instead of all the port LEDs.
548783 Some models support setting the mirror destination to “internal.” This is intended only for
debugging purposes and might prevent critical protocols from operating on ports being used
as mirror sources.
572052 Backup files from FortiSwitchOS 3.x that have 16-character-long passwords fail when
restored on FortiSwitchOS 6.x. In FortiSwitchOS 6.x, file backups fail with passwords longer
than 15 characters.
Workaround: Use passwords with a maximum of 15 characters for FortiSwitchOS 3.x and
6.x.
585550 When packet sampling is enabled on an interface, packets that should be dropped by uRPF
will be forwarded.
606044, 610149 The results are inaccurate when running cable diagnostics on the FS-108E, FS-124E, FS-
108E-POE, FS-108E-FPOE, FS-124E-POE, FS-124E-FPOE, FS-148E, and FS-148E-POE
models.
Bug ID Description
609375 The FortiSwitchOS supports four priority levels (critical, high, medium, and low); however,
The SNMP Power Ethernet MIB only supports three levels. To support the MIB, a power
priority of medium is returned as low for the PoE MIB.
support IPv6 features and cannot pass IPv6 protocol packets transparently.
l If you want to use IGMP snooping or MLD snooping with IPv6 features, you need to
enable set flood-unknown-multicast under the config switch global
command.
777647 l When MACsec is enabled on a tagged port, the set exclude-protocol command
does not work on packets with VLAN tags (ARP, IPv4, or IPv6).
l If you use the set exclude-protocol command with dot1q and packets with VLAN
tags (ARP, IPv4, or IPv6), the packets are not MACsec encrypted and are transmitted as
plain text.
l Only 0x88a8 type packets apply to qinq.
784585 When a dynamic LACP trunk has formed between switches in an MRP ring, the MRP ring
cannot be closed. Deleting the dynamic LACP trunk does not fix this issue. MRP supports
only physical ports and static trunks; MRP does not support dynamic LACP trunks.
Workaround: Disable MRP and then re-enable MRP.
l LLDP-assigned VLANs
l NAC
l Block intra-VLAN traffic
829807 eBGP does not advertise routes to its peer by default unless the set ebgp-requires-
policy disable command is explicitly configured or inbound/outbound policies are
configured.
903001 Do not use mgmt as the name of a switch virtual interface (SVI). mgmt is reserved for the
physical management switch port.
916405 FortiSwitchOS should not allow MACsec and 802.1X authentication to be configured on the
same port.
940248 When both network device detection (config switch network-monitor settings)
and the switch controller routing offload are enabled, the FS-1048E switch generates
duplicate packets.
Bug ID Description
978361 If restoring the FortiSwitch configuration from the GUI fails, the next firmware upgrade (using
the CLI or GUI) or configuration restore will fail.
Workaround:
1. Go to System > Config > Revisions and click Restore.
2. Choose the wrong configuration file and then click Apply.
You will see a “Failed to restore configuration.” error message.
3. Choose the right configuration file and then click Apply.
You will see a “Failed to restore configuration.” message.
4. Choose the right configuration file a second time and then click Apply.
You will see a “Settings successfully restored. Please wait while the system restarts.”
message.
987504 High CPU usage occurs on the FS-1xx series when the IGMP querier is enabled and IGMP
snooping is disabled.
Workaround: Disable the IGMP querier when IGMP snooping is not being used.
942068, 1006513 After using a dynamic port policy to remove or add a port, the profile was not updated after the
user logged out of the EAP session.
Copyright© 2025 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., in the U.S. and other jurisdictions,
and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and
other metrics contained herein were attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other
conditions may affect performance results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet
enters a binding written contract, signed by Fortinet’s General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance
metrics and, in such event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to
performance in the same ideal conditions as in Fortinet’s internal lab tests. In no event does Fortinet make any commitment related to future deliverables, features or development, and circumstances may
change such that any forward-looking statements herein are not accurate. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet
reserves the right to change, modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.